This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 31149

Summary:	[65cat] Add 'Auto commit' r/w property on Connection node
Product:	db	Reporter:	Martin Schovanek <mschovanek>
Component:	Code	Assignee:	Libor Fischmeistr <lfischmeistr>
Status:	NEW ---
Severity:	blocker	CC:	hmichel, hogi, kovica, krustyfur, misterm, rptmaestro, sansan, torkjel, vbrabant
Priority:	P2
Version:	3.x
Hardware:	All
OS:	All
Issue Type:	ENHANCEMENT	Exception Reporter:
Bug Depends on:
Bug Blocks:	152818, 65764

Description Martin Schovanek 2003-02-17 16:24:04 UTC

When you want to use transactions in the
Expolrer's Command Editor you must switch off
auto-commit mode on the DB connection. But this
prperty is missing in current implementation.

Comment 1 Martin Schovanek 2003-02-17 18:14:37 UTC

Another issue: Oracle by default creates temporary tables with option
'ON COMMIT DELETE ROWS' i.e. unusable with auto-commit mode.

Comment 2 David Vancouvering 2007-05-29 22:32:35 UTC

*** Issue 51412 has been marked as a duplicate of this issue. ***

Comment 3 Jiri Rechtacek 2009-10-16 14:06:39 UTC

Reassigned to new owner.

Comment 4 dwuysan 2011-03-10 21:34:31 UTC

We start to rely on Netbeans very very heavily. For example instead of starting the application server from scripts, we now simply start from the service tabs.

We also plan to stop (or minimise) the use of DB IDE such as TOAD or SQLDeveloper in favour of in-built editor. Unfortunately, the auto-commit is giving a lot of pain, particularly when debugging/testing SQL statements.

Comment 5 Jiri Rechtacek 2011-03-11 08:05:13 UTC

> We also plan to stop (or minimise) the use of DB IDE such as TOAD or
> SQLDeveloper in favour of in-built editor. Unfortunately, the auto-commit is
> giving a lot of pain, particularly when debugging/testing SQL statements.
Thanks for your feedback, I'll add this RFE among other issues to consider in planning phase.

Comment 6 matthias42 2011-10-23 20:20:47 UTC

*** Bug 76448 has been marked as a duplicate of this bug. ***

Comment 7 matthias42 2011-10-23 20:21:44 UTC

*** Bug 65764 has been marked as a duplicate of this bug. ***

Comment 8 matthias42 2012-04-17 19:03:26 UTC

*** Bug 152412 has been marked as a duplicate of this bug. ***

Comment 9 matthias42 2012-04-17 19:08:06 UTC

Note for potential implementers - comment 4 of bug 65764 looks like a good
proposal to follow. Additional thinks to consider:

- Should there be a central place to shutdown connections?
- Do connection leaks have to tracked?
- Should a connection pool be transparent? (=> each use could get a seperate
connection, which is shared until two parallel transactions are needed (either
by issuing a query while in autocommit mode or by beginning an explicit
transaction)

Comment 10 matthias42 2013-03-17 22:32:21 UTC

*** Bug 151686 has been marked as a duplicate of this bug. ***