Re: Problems with batch using jdbc on postgresql 7.4.2

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: "Manuel García H(dot)" <mgarciah(at)ife(dot)org(dot)mx>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Problems with batch using jdbc on postgresql 7.4.2
Date: 2004-04-15 04:39:18
Message-ID: 407E11F6.403@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Manuel García H. wrote:
> Hi, somebody can help me?
>
> I using a batch sentence to update some data in distinct tables, one of
> that tables have a foreing key, then when I execute the batch using jdbc
> on postgresql 7.4.2 abort the batch and send me the next message:
>
> ERROR: SPI_connect failed
> DEBUG: AbortCurrentTransaction
> LOG: statement: rollback; begin;
>
> the exactly sentence is a insert into table (,,,) values (,,,), the
> message was send just after execute the insert. If I removed the foreing
> key from the table , the batch worked correctly, but can´t drop the
> foreing key because I don´t want lost the integrity of data

On the face of it, this doesn't look like a JDBC problem: those messages
are not generated by the JDBC driver, and the driver does not do
anything special for INSERTs involving foreign keys.

What happens if you run the same transaction via psql?

-O

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Tom Lane 2004-04-15 04:44:20 Re: Problems with batch using jdbc on postgresql 7.4.2
Previous Message James Robinson 2004-04-15 03:13:22 JBoss and Statement Pooling endgame.