From: | Nelson Arape <narape(at)ica(dot)luz(dot)ve> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Statement has been closed (only in Windows) |
Date: | 2006-02-08 01:16:47 |
Message-ID: | 200602072116.47773.narape@ica.luz.ve |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
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é
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schaber | 2006-02-08 09:34:19 | Re: Inconsistent casting with literal vs parameter |
Previous Message | Matthew Bellew | 2006-02-08 00:16:39 | Re: Inconsistent casting with literal vs parameter |