Re: Statement has been closed (only in Windows)

Поиск
Список
Период
Сортировка
Искать
От
Nelson Arape
Тема
Re: Statement has been closed (only in Windows)
Дата
Msg-id
200602072116.47773.narape@ica.luz.ve
Ответ на
Список
Дерево обсуждения
Statement has been closed (only in Windows) Carlos Correia <carlos@m16e.com>
Re: Statement has been closed (only in Windows) pedro farinha <pedro@geotaxi.com>
Re: Statement has been closed (only in Windows) Carlos Correia <carlos@m16e.com>
Re: Statement has been closed (only in Windows) Nelson Arape <narape@ica.luz.ve>
El Martes, 7 de Febrero de 2006 19:09, Carlos Correia escribió:
> pedro farinha escreveu:
> | Hi Carlos, if you're problem is solved what is the question?
> | if you worry about creating a lot of statements, don't. But make sure
> | you close them after use. Also the resultSet if any. Not a big brain on
> | this end, but why would you want to keep the statement open?
>
> Well, why not? It's a fat client, It establishes a connection at
> application start up and closes it once the app finishes... what's the
> problem about keeping the same statement (it's been working like that in
> a production environment for years in Linux)?
>
Maybe your problem is more related to the transition from postgres (and its 
JDBC driver) from 7.x to 8.x.

Why not you try your migration in steps

1.	Migrate to Postgres 8.x (and its JDBC driver) on Linux
2.	Migrate from linux to windows.

I think that the step to may be easer than step 1 due to changes related to 
use network protocol version 3 and serverside prepare statement.

Nelson Arapé
В списке pgsql-jdbc по дате отправления
От: Matthew Bellew
Дата:
От: Markus Schaber
Дата:
FAQ