Re: Cannot turn off auto commit?

[email protected] Wed, 7 Sep 2016 21:17:01 +0000

Newsgroups	gmane.comp.java.hsqldb.user
Organization	io7m.com
Message-ID	<[email protected]>

Hello!

On 2016-09-07T22:08:06 +0100
Fred Toussi <[email protected]> wrote:
>
> A DDL statement is not transactional. A commit is executed implicitly
> both before and after the statement execution.
> 
> If you want to avoid the exception when the statement is executed the
> second time, use:
> 
> CREATE CACHED TABLE IF NOT EXISTS broken ...
> 
> Statements such as INSERT or DELETE are transactional and will be rolled
> back when you call rollback() on the connection.

That's bizarre. Has this always been the case?

I remember a few years back trying to decide between HSQLDB and H2, and
picking HSQLDB because DDL statements appeared to be transactional.

Without transactional DDL, how do I guarantee that my database is set
up correctly and atomically? With implicit commits, any failure means
that I end up with a half configured database that has to then be
destroyed and created from scratch.

M

------------------------------------------------------------------------------

_______________________________________________
Hsqldb-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hsqldb-user

signature.asc (application/pgp-signature, 821 B)