Hi,

i have a little mapping problem...



is not mapped like exspected to the database. That means all (not listed attributes) are mapped to a VERSIONDESCRIPTOR table and for the predecessor and successor list a second table VERSIONDESCRIPTOR _VERSIONDESCRIPTOR is created that contains versiondescriptor_uid, predecessor_uid and successor_uid.
BUT the problem is that these columns are configured as NOT NULL instead of NULLABLE. What can i do to resolve this issue ? For example - I am getting errors if i try to insert only a successor, because Hibernate tells me that there is no defaultvalue for the other (predecessor)...


Removing this restriction directly on the DB works fine and i can produce something like this:


I already thought about telling Hibernate to create two seperate tables for it... but how? or is there a simpler solution ?

Cheers Tobias

@JoinTable did the job :)

Well if it works, then that's good.

It seems like you might map things differently, though, with less records and less columns. As it is, you have two rows for each predecessor/successor relationship, right? And you always have one NULL in either the predecessor (P) or successor (S) column, right?

How about modeling it with one table, where each row represents a P/S relationship. The table has only two columns - P and S. The predecessors relationships of an object are represented by those rows where the object's ID appears in the P column. Its successor relationships are represented by the rows where it appears in the S column.

You'd have half the records, and one less column. Referential integrity would be easier to maintain, I'd figure.

You think?

-larry