[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-414) Informix dialect creates syntax errors in IDS 9.4

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Fri, 24 Oct 2003 11:03 AM
       Body:
Please provide a patch for this.

Typing/copying code from a comment is so much harder and errorprone compared to a good old patch ;)


---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-414


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-414
    Summary: Informix dialect creates syntax errors in IDS 9.4
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0.2

   Assignee: 
   Reporter: Finn McCann

    Created: Tue, 21 Oct 2003 11:01 AM
    Updated: Tue, 21 Oct 2003 11:01 AM
Environment: Hibernate2 on JDK1.4 on Win2000, talking via Informix JDBC 2.21.JC5 driver to Informix IDS 9.4 on another Windows 2000 box.

Description:
Having tested Informix dialect in Hibernate2 against Informix IDS v9.4, we found a couple of issues: 

1.  Serial ids:

<id name="id" column="ID" length="32" unsaved-value="null">
   <generator class="uuid.hex"/>
</id>

creates a data type:

INT8 SERIAL   

instead of:

SERIAL8

The "INT8 SERIAL" causes a syntax error in IDS 9.4.

2. Foreign Key constraint names:

<set name="upliftRates" lazy="true" cascade="all" order-by="EFFECTIVE_DATE desc">
        <key column="NETWORK_ID" length="32"/>
        <one-to-many class="com.capetechnologies.multinet.domain.UpliftRate"/>
</set>

creates this ALTER TABLE statement:

alter table MULTINET_TAX_RATES add constraint FKE1700D046924EC foreign key (NETWORK_ID) references MULTINET_NETWORK

instead of:

alter table MULTINET_TAX_RATES add constraint foreign key (NETWORK_ID) references MULTINET_NETWORK constraint FKE1700D046924EC

Having "CONSTRAINT <constraint name>" within the statement instead of at the end causes a syntax error.

This also applies to adding UNIQUE CONSTRAINTs.



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira