I have a table mapped as follows:
class-descriptor class=com.gearlist.gear.ojb.GearPhotoDataInstance
table=gl_gear_photo_data
field-descriptor name=gearPhotoNbr column=gear_photo_nbr
jdbc-type=INTEGER/
field-descriptor name=photoData column=photo_data
jdbc-type=BINARY/
/class-descriptor
I double-checked the configuration of my tests and realized I was running
tests on a subclass, not the original User class that gets the wrong
sequence numbers.
So I dropped back and ran just the superclass. Everything worked fine; the
sequence numbers were assigned correctly. So the
Armin Waibel said:
Hi Robert,
there is bug in ODMG-api FK assignment when using
SequenceManagerNativeImpl (using DB Identity columns).
Test case is in CVS and we will try to fix this problem asap.
workaround: use the PB-api to insert new object with 1:1 reference
I'm not sure I
Armin Waibel said:
Robert Crawford wrote:
Armin Waibel said:
Do you only use the PB-api? This bug is odmg-api related.
I only use the PB-api.
Then you shouldn't get problems with negative sequence numbers.
Can you describe me with some pseudo code an test case to reproduce your
Armin Waibel said:
Robert Crawford wrote:
Armin Waibel said:
Robert Crawford wrote:
Armin Waibel said:
Do you only use the PB-api? This bug is odmg-api related.
I only use the PB-api.
Then you shouldn't get problems with negative sequence numbers.
Can you describe me with some pseudo
Charles N. Harvey III said:
It means that something isn't set correctly in the database.
This has happened to me many times. It always happens when I turn on
native sequencing (IDENTITY in MSSQL or AUTOINCREMENT in MySql).
Check the PK of your database, it might not be properly set to
I'm using database sequence numbers with MySQL, and keep getting negative
numbers for the primary keys. I understand these are coming from a
temporary sequence ID used by OJB, but I thought that setting the right
platform, sequence manager, and field attributes (primarykey=true
autoincrement=true
