[Bug 56586] initSQL should be committed if defaultAutoCommit == false

2014-07-24 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56586 --- Comment #7 from Craig Servin --- I can't think of any issues with that unless someone was intentionally trying to lose their initSQL later on. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 56586] initSQL should be committed if defaultAutoCommit == false

2014-07-24 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56586 --- Comment #6 from Filip Hanik --- Thanks for the report gentlemen. Glad there is a workaround, the added ";commit". If it did do if ( !connection.getAutoCommit() ) connection.commit(); what are the implications for other users? -- Y

[Bug 56586] initSQL should be committed if defaultAutoCommit == false

2014-07-24 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56586 --- Comment #5 from Wes Clark --- I agree with the filer. Alternately, turn on autocommit when running the initialization SQL, then if configured to be off, turn it back off. -- You are receiving this mail because: You are the assignee f

[Bug 56586] initSQL should be committed if defaultAutoCommit == false

2014-06-05 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56586 --- Comment #4 from Craig Servin --- It just seems like the connection initialization should persist for the life of the connection. If I have some DML that initializes a connection, and it is returned to the pool, when I use that connecti

[Bug 56586] initSQL should be committed if defaultAutoCommit == false

2014-06-05 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56586 --- Comment #3 from Christopher Schultz --- Honestly, I'm surprised that "SET search_path [..]" will be affected by a rollback. I know it's no basis for comparison, but MySQL does not appear to behave this way: mysql> begin; Query OK, 0 r

[Bug 56586] initSQL should be committed if defaultAutoCommit == false

2014-06-05 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56586 --- Comment #2 from Craig Servin --- I am using postgresql and the problem originally showed up when the initSQL was executing a set search_path and a rollback was triggered by the first transaction. To test/recreate the issue I did trigge

[Bug 56586] initSQL should be committed if defaultAutoCommit == false

2014-06-04 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56586 --- Comment #1 from Christopher Schultz --- Are you executing DML statements in your initSQL? Are there drivers who allow rollbacks on session state changes? Weird. Note that you could always use a stored procedure that contains a COMMIT