One of the basic reasons behind using IDBroker over the optimized native
variations of generating primary keys was that it could allow a range of
IDs to be reserved, so that it was not necessary to query and write to
the single ID_TABLE for every insert into the database. If the IDs are
not conflicting with current rows and the quantity column has a value
high enough to account for the lower IDs still being used, then I would
suspect that is the cause.
John McNally
[EMAIL PROTECTED] wrote:
For one of our J2EE application using Torque, we have accidentaly deleted
the ID_TABLE on our Oracle Server. After we noticed the problem, we have
recreated ant repopulated the table whit next-id field values far higher
than the ones already used for all the tables in the database.
After the problem, Torque as created records whith id values < next-id
values defined when repopulating the ID_TABLE.
Note that our application server hasn't been restarted since the problem
occur.
Does anybody know why this is possible ?
Bernard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
