From: SourceForge.net <no...@so...> - 2003-12-03 22:37:27
|
Bugs item #834293, was opened at 2003-11-01 20:42 Message generated for change (Comment added) made by kal_ahmed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=391879&aid=834293&group_id=27895 Category: Hibernate Impl Group: None >Status: Pending >Resolution: Fixed Priority: 5 Submitted By: Florian G. Haas (haasfg) Assigned to: Nobody/Anonymous (nobody) Summary: Hibernate test suite fails with HypersonicSQL Initial Comment: Running the Hibernate test suite (ant -Dbackends="hibernate" tm4j-test) with HypersonicSQL produces the same error over and over again. Apparently hsqldb is complaining about a foreign key constraint violation. The TMOBJECTS table does contain an line where the value of "ID" is 'ff808081f898ec9900f898ecb6280033', whereas the TOPICMAPS table does not contain a line where the value of "BASELOCATOR" is 'ff808081f898b79b00f898b7bc890039'. So it makes sense for the database to complain about the FK constraint being violated. Question is, why is there no line in TOPICMAPS with the appropriate value for "BASELOCATOR"? ---------------------------------------------------------------------- >Comment By: Kal Ahmed (kal_ahmed) Date: 2003-12-03 22:37 Message: Logged In: YES user_id=176992 It seems that the problem was that both tmobjects and topicmaps had the srclocs.tmobject_id column as a foreign key. My guess is that trying to use srclocs to do many-to-many mappings between the tmobjects and locators table *and* the topicmaps and locators table was probably not the right thing to do. I've changed the mapping file for the TopicMapDataObject so that it now uses a separate table (tmsrclocs) for its many-to-many relationship with the locators table. Can you retest on your installation to validate that this fixes the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=391879&aid=834293&group_id=27895 |