Hi all, I'm using the High/low sequence manager with one of my applications and I noticed that it sometimes decreases the MAX_KEY field without any reason. I'm not an expert of this algorithm but I don't think it's a normal behavior. Here is a sample of the P6SPY log, when the MAX_KEY decreases (the name of the table is UNITE_TEMPS_UTE and the primary key is UTE_ID, the value jumps from 29108 to 28959):
03 mars 2005 - 17:14:54,594 - 1109866494594|1|7|statement|select max_key,tablename,grab_size,version,fieldname from ojb_hl_seq where tablename = ? and fieldname = ? |select max_key,tablename,grab_size,version,fieldname from ojb_hl_seq where tablename = 'seq_unite_temps_ute' and fieldname = 'ute_id' 03 mars 2005 - 17:14:54,596 - 1109866494596|1|7|statement|update ojb_hl_seq set max_key=?,grab_size=?,version=? where tablename = ? and fieldname = ? and version = ? |update ojb_hl_seq set max_key='29108',grab_size='1',version='0' where tablename = 'seq_unite_temps_ute' and fieldname = 'ute_id' and version = '0' 03 mars 2005 - 17:15:02,850 - 1109866502850|1|4|statement|select a0.max_key,a0.tablename,a0.grab_size,a0.version,a0.fieldname from ojb_hl_seq a0 where (a0.tablename like ? ) and a0.fieldname like ? |select a0.max_key,a0.tablename,a0.grab_size,a0.version,a0.fieldname from ojb_hl_seq a0 where (a0.tablename like 'seq_unite_temps_ute' ) and a0.fieldname like 'ute_id' 03 mars 2005 - 17:15:02,851 - 1109866502851|-1||resultset|select a0.max_key,a0.tablename,a0.grab_size,a0.version,a0.fieldname from ojb_hl_seq a0 where (a0.tablename like 'seq_unite_temps_ute' ) and a0.fieldname like 'ute_id' |fieldname = ute_id, grab_size = 1, tablename = seq_unite_temps_ute, version = 0 03 mars 2005 - 17:15:02,852 - 1109866502852|1|4|statement|select max_key,tablename,grab_size,version,fieldname from ojb_hl_seq where tablename = ? and fieldname = ? |select max_key,tablename,grab_size,version,fieldname from ojb_hl_seq where tablename = 'seq_unite_temps_ute' and fieldname = 'ute_id' 03 mars 2005 - 17:15:02,854 - 1109866502854|1|4|statement|update ojb_hl_seq set max_key=?,grab_size=?,version=? where tablename = ? and fieldname = ? and version = ? |update ojb_hl_seq set max_key='28959',grab_size='1',version='0' where tablename = 'seq_unite_temps_ute' and fieldname = 'ute_id' and version = '0' That's a really annoying issue as OJB makes UPDATE queries instead of INSERT on the recovery interval and mess up the whole database. I use OJB 1.0 rc4 and OJB is the only application making INSERT on this table. Thanks in advance. Arno --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
