Tickets :: Comment on [#13876] horde_histories

* Your Email Address
* Spam protection	Enter the letters below: .___.___..___.__..___ [__ _/ [__ [__][__ [___./__.[___\| \|[___
Comment	> I had a new history_modseq reset in the same database just some days > ago. My current modseq should be right now over 550000, but it shows > just about 6000. > I'm almost sure that it is some sort of "race condition" when server > load is too high, as I explained before. > > I'm trying the following patch, to prevent "horde_histories_modseq" > table to become empty. > It really doesn't change anything, as I guess code executes deletes > in "horde_histories_modseq" table because old data there is useless. > > --- a/Horde/History/Sql.php 2015-03-06 10:10:49.075159565 +0100 > +++ b/Horde/History/Sql.php 2015-03-06 10:11:20.547151406 +0100 > @@ -355,7 +355,7 @@ > { > try { > $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)); > + $this->_db->delete('DELETE FROM horde_histories_modseq > WHERE history_modseq < (? - 25)', array($result)); > } catch (Horde_Db_Exception $e) { > throw new Horde_History_Exception($e); > } > >
Attachment
Watch this ticket