We¹re using 1.6.0 against Oracle with a model like this:
Entity A
{
-...@b myB;
}
Entity B
{
String X;
String Y;
}
In the generated DDL, I¹m seeing the constraint being applied the wrong way
(and the table and hibernate mappings being generated the wrong way).
Specifically, the table declaration for A has a B column (to store B¹s ID)
and a foreign key is generated against it.
ALTER TABLE A ADD CONSTRAINT FK_A_B FOREIGN KEY (B) REFERENCES B (ID) ;
If I make it bidirectional, a foreign key is each way.
If I make it one-to-many, it works correctly.
What am I missing? Shouldn¹t I expect to see the FK on table B? Its
impossible to delete Bs...
Thanks in advance for the assistance.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Fornax-developer mailing list
Fornax-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fornax-developer
