Hi, I'm having problem with the following hibernate mapping, and hoping someone could suggest a solution or a way to work around it.






Using the above mappings I end up with a table called "positionList", and it has six columns namely:

OwnerOne_positionList_FK,
positionList_index,
positionList_x,
positionList_y,
positionList_z,
OwnerTwo_positionList_FK

When I create an instance of OwnerOneBO and added a Position object to the positionList attribute I get the following exception:

net.sf.hibernate.JDBCException: Could not synchronize database state with session: Try to insert null into a non-nullable column in statement [insert into positionList (OwnerOne_positionList_FK, positionList_index, positionList_x, positionList_y, positionList_z) values ('E0ED0A1C-9B62-7A0A-82F7-27CA9A21CD08', 0, 0.0E0, 0.0E0, 0.0E0)]

In other words, it's complaining that I didn't specify "OwnerTwo_positionList_FK" column. But that was indeed my intention to leave the "OwnerTwo_positionList_FK" column as null when the positionList created belongs to OwnerOneBO.

Apart from giving the two list elements distinctive names. Does anyone know if there is property I can set to tell Hibernate to ignore "OwnerTwo_positionList_FK" when I create an instance of OwnerOneBO. Or does anyone know any other way to work around this
issue?

Regards,

KC

It might be that you have a not null constraint on that column in the database that you didn't intend?

Indeed, there is a not null constraint on the "OwnerTwo_positionList_FK" column, but that is something I have no control of.

The problem is I have two different classes: OwnerOneBO and OwnerTwoBOl; and both have a collection(List) of the Position class and they both call this collection(List) attribute as positionList. So I end up with a table with the following columns:

OwnerOne_positionList_FK (Not Null),
positionList_index,
positionList_x,
positionList_y,
positionList_z,
OwnerTwo_positionList_FK (Not Null)

And when I create an instance of OwnerOneBO , the column OwnerTwo_positionList_FK has to be null!

Any one can help? Many thanks!

If its possible and normal that that one or the other column will be null, then how is this a valid NOT NULL constraint? Sounds like an FK constraint would be a better choice than a NOT NULL constraint.

Sorry, I think I have confused everyone, because I thought it was Hibernate's default to set the FK constrain together with the NOT NULL constraint, and that's why I'm getting the exception:

Try to insert null into a non-nullable column in statement [insert into positionList (OwnerOne_positionList_FK, positionList_index, positionList_x, positionList_y, positionList_z) values ('E0ED0A1C-9B62-7A0A-82F7-27CA9A21CD08', 0, 0.0E0, 0.0E0, 0.0E0)]

Or perhaps that is a default by the Hypersonic Database Engine...? I will check...

But Hibernate does not do anything with constraints; or are you talking about the schema generator?

And besides you would want an FK constraint instead of a NOT NULL constraint.