Tickets :: Comment on [#13876] horde_histories

* Your Email Address
* Spam protection	Enter the letters below: .__ . . .. .___ [__)\|_/ \|\| [__ [__)\| \\__\|\|___[___
Comment	> I guess you make "manually inserting keys" when carrying out > migration of databases. On a daily use, you don't have to make manual > inserts in a sequence controlled column, as sequence is up to date by > its own. Maybe you can check if a "manual insert" on primary key is > being done, before calling resetPkSequence. > > I think the problem with history_modseq reset must be a call to > resetPkSequence when horde_history_modseq table was empty (no rows at > all). > Your code would then reset primary key to '1'. Is this right? > > But this table can be empty if enough processes are running at the > same time. Function _nextModSeq at "Horde/History/Sql.php" makes > inserts and also deletes: > ... > $result = $this->_db->insert('INSERT INTO horde_histories_modseq > (history_modseqempty) VALUES(0)'); > $this->_db->delete('DELETE FROM horde_histories_modseq WHERE > history_modseq <> ?', array($result)); > ... > > One process may have $result==3, and will delete others row. > A second one may have $result==4, and will delete the previous one. > Now horde_history_modseq table can be empty. > And a third process can be making a call to resetPkSequence just by > then, finding no data at all and reseting sequence to '1'. > > In my database, just before the reset, there are two login errors in > horde_histories with the very same timestamp and consecutive modseq > values (the highest value before the reset). Maybe those events > cleaned horde_history_modseq table while a third process was calling > resetPkSequence.
Attachment
Watch this ticket

Saved Queries