On Wed, 21 Jan 2004 09:34:15 -, fredt <[EMAIL PROTECTED]>
wrote with possible deletions:
Thanks Fred.
There is no major difference between HSQLDB's understanding of a
transaction
and the general use of this. As you say a transaction is basically what
happens between two ROLLBACK/COMMIT co
January 2004 08:29
Subject: Re: [Hsqldb-developers] Nested transactions not grouped in a parent
transaction
On Tue, 20 Jan 2004 22:59:34 -, fredt <[EMAIL PROTECTED]>
wrote with possible deletions:
> This looks more like a code review :)
well, I think it's the only way to get used
On Tue, 20 Jan 2004 22:59:34 -, fredt <[EMAIL PROTECTED]>
wrote with possible deletions:
This looks more like a code review :)
well, I think it's the only way to get used to ;-)
The difference between nested transaction and others should be obvious.
If
autocommit is false, you want the l
This looks more like a code review :)
The following two commands are executed as nested transactions:
INSERT INTO ... SELECT... FROM ..
UPDATE ...
The reason INSERT and DELETE are not, is because adequate checks for
referential integrity and NOT NULL constraints could be performed without
insert
