[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-742?page=co...
]
Miroslav Havram commented on ANN-742:
-------------------------------------
No, I didn't - I've just used annotations proposed by Hardy and got that result...
Anyway, where do you mean I should put it?
Just to be sure - I want to have (0..1) <-> (0..1) association and that association
should be mapped to the join table. Also, it should be possible for both entities to to
exist independently on each other. Currently it is not possible to achieve such behavior
as Address cannot be persisted if it is not linked to Person.
Maybe it will be the best to open another issue as this is not related to the initial
problem...
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
Assignee: Hardy Ferentschik
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira