Re: Mail an JDBC driver - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: Mail an JDBC driver
Date
Msg-id CADK3HHJkXjjP+yf+74_nR-TzA-FR-1+ZwWzDysOtStKQ7CWw7A@mail.gmail.com
Whole thread Raw
In response to Re: Mail an JDBC driver  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-jdbc
Could be because we now cache statements. I suspect the cached statement would not like you switching the schema out from under it.

How are you changing the search path? Ideally if you use setSchema we may have to look at invalidating the cache. Vladimir ?


On 2 August 2016 at 08:27, David G. Johnston <david.g.johnston@gmail.com> wrote:
On Tue, Aug 2, 2016 at 3:31 AM, KUNES Michael <Michael.KUNES@frequentis.com> wrote:
If you need more information, please let us know.

​Is the same DB version (and which exact versions) being used in both tests?  I strongly suspect no...

Can you turn on full statement logging and see if anything unusual shows up?

​What's in your WHERE clause on the delete - and did you use Statement or PreparedStatement?

Having a self-contained test case makes the previous two items less problematic.  Also, that general test case can be translated to psql which would help to isolate the problem to either the driver or the database.

​David J.​


pgsql-jdbc by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Mail an JDBC driver
Next
From: Dave Cramer
Date:
Subject: Re: Mail an JDBC driver