[hibernate-issues] [Hibernate-JIRA] Updated: (ANN-742) Primary key should not be set on nullable column

[Emmanuel Bernard (JIRA)]

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

Emmanuel Bernard updated ANN-742:
---------------------------------

    Fix Version/s: 3.4.0.CR2

> Primary key should not be set on nullable column
> ------------------------------------------------
>
>                 Key: ANN-742
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-742
>             Project: Hibernate Annotations
>          Issue Type: Bug
>          Components: binder
>    Affects Versions: 3.3.1.GA
>         Environment: hibernate core 3.2.6.GA
>            Reporter: Miroslav Havram
>             Fix For: 3.4.0.CR2
>
>         Attachments: create_scripts.zip, test_case.zip
>
>
> After switching to hibernate-annotations 3.3.1.GA, DDL generated for intermediate table for optional one-to-one association tries to set
> primary key on nullable column. Problem is that some DBMSs (e.g. MS SQL) do not allow that.
> Using hibernate-annotations-3.3.0.GA:
> create table personAddress (address_id bigint not null, person_id bigint not null, primary key (person_id))
> Using hibernate-annotations-3.3.1.GA:
> create table personAddress (person_id bigint, address_id bigint, primary key (person_id))
> Simple test case and generated DDLs are attached.

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