Don't use dummy dual table for hsqldb (David Balažic)

Description

This removes creation and use of a dual_foo table for each sequence.
It is a simplification and also solves failures due to white space before the sequence name in the mapping XML :

<id name="id" type="long" column="ID">
<generator class="sequence">
<param name="sequence">
seq_bar
</param>
will fail in the old code :

"create table dual_" + sequenceName + " (zero integer)"

which would give the following bad SQL :

create table dual_
seq_bar
(zero integer)

Environment

hibernate 3.2.5
hsqldb 1.8.0.1

Activity

Show:
Steve Ebersole
September 13, 2007, 1:25 PM

I asked you on the dev list to determine the hsqldb version in which support for this was added. Which is it?

David Balažic
September 13, 2007, 1:54 PM

1.8.0.1 supports it.
the changelog for 1.8.0.0-1.8.0.1 does not mention adding any new feature like this.
And versions before 1.8.0.0 are not supported by HSQLDialect anyway.

I tried now v 1.7.3 and it also supports the "call next value for seq_name" syntax.

David Balažic
October 2, 2007, 2:13 PM

fredt (tha main hsqldb guy, as I understand) said :

"It appeared in 1.7.2"

(see http://article.gmane.org/gmane.comp.java.hsqldb.user/3718 for reference)

Steve Ebersole
October 3, 2007, 4:51 AM

applied to 3.2/trunk

thanks

Assignee

Steve Ebersole

Reporter

David Balažic

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Affects versions

Priority

Major
Configure