Solution: Problem (Bug?): Inheritance / Mapping Classes on Multiple Joined Tables / Primary Key is _NOT_ auto-increment

2004-07-28 Thread Sven Woltmann
ersistentFields", fields where not computed as "inherited persistent fields" if they were primary keys. This if-clause has been completely removed. A new version seems to be released in a few days. Sven -----Original Message- From: Sven Woltmann [mailto:[EMAIL PROTECTED] Sent

Problem (Bug?): Inheritance / Mapping Classes on Multiple Joined Tables / Primary Key is _NOT_ auto-increment

2004-07-28 Thread Sven Woltmann
Hello, I have a problem with an inheritance hierarchy, mapped on multiple joined tables, where the primary key is _not_ auto-increment. The problem is: OJB always stores "0" as the value for the primary key field, although I defined another value. To make this easily reproducable, I c