[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-2839) Don't use dummy dual table for hsqldb (David Balažic)
Steve Ebersole (JIRA)
noreply at atlassian.com
Tue Oct 2 22:52:25 EDT 2007
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Ebersole closed HHH-2839.
-------------------------------
Resolution: Fixed
applied to 3.2/trunk
thanks
> Don't use dummy dual table for hsqldb (David Balažic)
> -----------------------------------------------------
>
> 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
> Assignee: Steve Ebersole
> Fix For: 3.2.6, 3.3
>
> 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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list