Re: JDBC gripe list (the autocommit subthread)

From: Quartz <quartz12h(at)yahoo(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: JDBC gripe list (the autocommit subthread)
Date: 2011-03-31 14:40:08
Message-ID: 591177.72544.qm@web33202.mail.mud.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

> The docs say something completely at odds with your
> assertion:
>
> a JDBC driver may or may not continue to process the
> remaining commands in the batch. However, the driver's behavior
> must be consistent with a particular DBMS, either always
> continuing to process commands or never continuing to process
> commands.

Then let's simplify the whole discussion:

If I issue statement 1, 2 and 3, and statement 2 fails, there is no prescribed behavior for statement 3, but one sure thing is the statement 1 must be completed. This is exactly where postgres driver fails. I have nothing else to say.

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2011-03-31 14:47:36 Re: JDBC gripe list
Previous Message Andrew Hastie 2011-03-31 14:20:20 Re-read of updated row using scrollable ResultSet returns old data