[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2839?page=c...
]
David Balažic commented on HHH-2839:
------------------------------------
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.
Don't use dummy dual table for hsqldb
-------------------------------------
Key: HHH-2839
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2839
Project: Hibernate3
Issue Type: Patch
Affects Versions: 3.2.5
Environment: hibernate 3.2.5
hsqldb 1.8.0.1
Reporter: David Balažic
Attachments: HSQLDialect.diff
Original Estimate: 2 hours
Remaining Estimate: 2 hours
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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira