on 12/10/07 2:27 PM, [EMAIL PROTECTED] purportedly said:
>>> To work around this I add an dbCon.rollBack() after select statement
>>> above in good and in bad times. After that ALTER works.
>>> Can someone explain me why I need this rollback ?
>>
>> You only need the rollback when the SELECT stat
On Dec 10, 2007 2:48 PM, Keary Suska <[EMAIL PROTECTED]> wrote:
> on 12/10/07 12:15 PM, [EMAIL PROTECTED] purportedly said:
>
> > To work around this I add an dbCon.rollBack() after select statement
> > above in good and in bad times. After that ALTER works.
> > Can someone explain me why I need th
On Mon, Dec 10, 2007 at 08:13:09PM +0100, Thomas Carsten Franke wrote:
> If I do so I get following error by Postgres:
>
> org.postgresql.util.PSQLException: ERROR: current transaction is
> aborted, commands ignored until end of transaction block
It means exactly what it says. You (or Java for yo
on 12/10/07 12:15 PM, [EMAIL PROTECTED] purportedly said:
> To work around this I add an dbCon.rollBack() after select statement
> above in good and in bad times. After that ALTER works.
> Can someone explain me why I need this rollback ?
You only need the rollback when the SELECT statement fails
Hi,
following I tried for some application logic based data migration
Statement stmt = dbCon.createStatement();
try {
ResultSet geo_columns_rs = stmt.
executeQuery("SELECT baseline_check_version from geodb limit 1");
source_version = Versions.R03_00;
source_version = Versi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
following I tried for some application logic based data migration
Statement stmt = dbCon.createStatement();
try {
ResultSet geo_columns_rs = stmt.
executeQuery("SELECT baseline_check_version from geodb limit 1");
source_vers
