[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-1860) Autogeneration of primary keys for Sybase IDENTITY columns fails with latest jConn3 driver

[Gail Badner (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gail Badner resolved HHH-1860.
------------------------------

      Assignee: Gail Badner
    Resolution: Rejected

This was a bug in jConnect which has been fixed.

> Autogeneration of primary keys for Sybase IDENTITY columns fails with latest jConn3 driver
> ------------------------------------------------------------------------------------------
>
>                 Key: HHH-1860
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1860
>             Project: Hibernate Core
>          Issue Type: Bug
>    Affects Versions: 3.2.0 cr1
>         Environment: JBoss 4.0.4GA, Adaptive Server Anywhere 9, jConnect using com.sybase.jdbc3.jdbc.SybDriver / jConn3.jar
>            Reporter: Erica Kane
>            Assignee: Gail Badner
>            Priority: Minor
>
> Sybase provides an IDENTITY column which is very useful for autogenerating primary keys for entity beans.  However, if version 6.05 of jConnect (the standard Sybase driver) is used, with com.sybase.jdbc3.jdbc.SybDriver, all inserts fail with a message that it was not possible to obtain the generated identity.
> Changing the datasource configuration to use com.sybase.jdbc2.jdbc.SybDriver fixes the problem.
> Hopefully this can be fixed -- I realize it may be Sybase's fault -- but if not, I hope this spares someone else the agony of figuring it out.

-- 
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