On Thu, 17 Sep 2009, Joseph Shraibman wrote:
[when passing a multi-statement sql string to executeUpdate, if a
statement after the first is a select, it is silently not fully
executed.]
Running queries in executeUpdate is not allowed. If you pass a plain
select to executeUpdate it complai
Craig Ringer wrote:
On Tue, 2009-09-15 at 19:26 +, Joseph Shraibman wrote:
The following bug has been logged online:
While the test case is appreciated, it's not really that clear what's
expected to happen vs what happens, at what point things go wrong and
under what circumstances, etc. L
On Tue, 2009-09-15 at 19:26 +, Joseph Shraibman wrote:
> The following bug has been logged online:
>
> Bug reference: 5058
> Logged by: Joseph Shraibman
> Email address: j...@selectacast.net
> PostgreSQL version: 8.2.14
> Operating system: Linux
> Description:[jdbc
On Tue, Sep 15, 2009 at 3:26 PM, Joseph Shraibman wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5058
> Logged by: Joseph Shraibman
> Email address: ...@selectacast.net
> PostgreSQL version: 8.2.14
> Operating system: Linux
> Description: [jdbc]
The following bug has been logged online:
Bug reference: 5058
Logged by: Joseph Shraibman
Email address: j...@selectacast.net
PostgreSQL version: 8.2.14
Operating system: Linux
Description:[jdbc] Silent failure with executeUpdate()
Details:
I was trying to figure ou
