9:22 a.m.
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
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
1:38 p.m.
New subject: [Hibernate-JIRA] Updated: (ANN-742) Primary key should not be set on nullable column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-742?page=co...
]
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:22 a.m.
New subject: [Hibernate-JIRA] Assigned: (ANN-742) Primary key should not be set on nullable column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-742?page=co...
]
Hardy Ferentschik reassigned ANN-742:
-------------------------------------
Assignee: Hardy Ferentschik
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
5:44 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-742) Primary key should not be set on nullable column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-742?page=co...
]
Hardy Ferentschik commented on ANN-742:
---------------------------------------
I've added the test case to the source code. I am not quite sure what could trigger
this behavior just by changing from 3.3.0.GA to 3.3.1.GA.
As a workaround one can add "nullable = false" to the inverse join column
definitions.
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
5:54 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-742) Primary key should not be set on nullable column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-742?page=co...
]
Hardy Ferentschik commented on ANN-742:
---------------------------------------
As far as I can see buildJoinColumn() is called twice to construct the column instances
for person_id and address_id. No special care is taken here about a 'nullability'.
This mean that the default value true from Ejb3Column applies. Later
Configuration.generateSchemaCreationScript() and Table.sqlCreateString() get called. The
latter contains the following lines:
if ( col.isNullable() ) {
buf.append( dialect.getNullColumnString() );
}
else {
buf.append( " not null" );
}
Seems that in order to get a 'not null' the dialect does not play a role. It is
just important whether the column instance is nullable. Not sure if I am missing
something.
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
9:17 a.m.
New subject: [Hibernate-JIRA] Resolved: (ANN-742) Primary key should not be set on nullable column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-742?page=co...
]
Hardy Ferentschik resolved ANN-742.
-----------------------------------
Resolution: Fixed
There was a actual bug in the code which is fixed now, but the given mapping in the test
case was incorrect as well. A bidirectional OneToOne association should be mapped the
following way:
@Entity
public class Person {
@Id
private long id;
@OneToOne
@JoinTable(
name = "personAddress",
joinColumns = @JoinColumn(name = "person_id"),
inverseJoinColumns = @JoinColumn(name = "address_id")
)
private Address address;
...
}
@Entity
public class Address {
@Id
private long id;
@OneToOne(mappedBy = "address")
private Person person;
...
}
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
6 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-742) Primary key should not be set on nullable column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-742?page=co...
]
Miroslav Havram commented on ANN-742:
-------------------------------------
I cannot agree with that because usage of the given mapping produces unacceptable DDL
(with both hibernate-annotations 3.3.0.GA and 3.3.1.GA):
create table personAddress (person_id bigint not null, address_id bigint, primary key
(address_id))
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
6:40 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-742) Primary key should not be set on nullable column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-742?page=co...
]
Hardy Ferentschik commented on ANN-742:
---------------------------------------
That's correct with 3.3.0.GA and 3.3.1.GA you won't get the correct DDL. As said,
there was also a bug which is fixed now. The fix will be available with the next release.
The given example is how a OneToOne association with join table should be mapped.
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
7:41 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-742) Primary key should not be set on nullable column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-742?page=co...
]
Miroslav Havram commented on ANN-742:
-------------------------------------
OK, I've checked out latest version from the repository and it now generates correct
DDL.
Now I have experienced annoter issue - instance of Address cannot be persisted if it is
not linked to Person - and that is not expected behavior, I want to have (0..1) <->
(0..1) association...
For example, this will not gona work:
Address a = new Address();
session.save(a);
it will report:
org.hibernate.PropertyValueException: not-null property references a null or transient
value: test.Address.person
I'm not really sure is it possible to express it using "mappedBy"...
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
2:42 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-742) Primary key should not be set on nullable column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-742?page=co...
]
Diego Plentz commented on ANN-742:
----------------------------------
Miroslav, you probably forgot to set a not null relationship. Check again, please.
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
4:17 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-742) Primary key should not be set on nullable column
[
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
3:17 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-742) Primary key should not be set on nullable column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-742?page=co...
]
Hardy Ferentschik commented on ANN-742:
---------------------------------------
Yes, I think a new Jira issue would be the best.
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
2:38 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-742) Primary key should not be set on nullable column
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-742?page=co...
]
Gail Badner commented on ANN-742:
---------------------------------
https://jira.jboss.org/jira/browse/JBPAPP-1859
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
5741
days inactive
6060
days old
hibernate-issues@lists.jboss.org
12 comments
5 participants
participants (5)
-
Diego Plentz (JIRA) -
Emmanuel Bernard (JIRA)
-
Gail Badner (JIRA)
-
Hardy Ferentschik (JIRA)
-
Miroslav Havram (JIRA)