[ BUILD # : Beta ]
[ JDK VERSION : 1.5.0_05 ]
[I am using the Derby Engine.]
When you are in the SQL Editor, would be nice to have a Commit/Rollback options.
Seems that it's always COMMIT by default. After each modification.
Yeah, the connection has autoCommit set to true. And what's worse, the
connection is shared among the database explorer and the SQL editor, so I can't
set it to false while executing SQL statements, as it would interfere with
actions in the database explorer. Either disable the database explorer while
executing SQL statements, or change the architecture to enable multiple connections.
IMO, if you support at least this feature per connection (even shared), it will help us a lot. Please, consider it for
I recognize the value of this feature, but it requires some serious thought and probably rework of our architecture. I
just don't know if we can commit to getting to it. But your vote has impact, it definitely raises the priority, so
thank you. I'll put it high on our "we should really do this" list.
I don't think we can do it without using a connection pool because otherwise we will cause a regression in the uses of
the Database Explorer API.
Basically what we need is to add a connection pool to each DatabaseConnection, and then add a new method called
getJDBCConnectionFromPool(). The existing getJDBCConnection() would behave as before, working with a single shared
connection, but new users of the DB Explorer should use getJDBCConnectionFromPool(), and existing users (like the SQL
editor) can be rewritten to use this and thus allow per-session settings like Autocommit.
Reassigned to new owner.
*** This bug has been marked as a duplicate of bug 31149 ***