Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#587 Presence DB save fails after one failure

ver 1.5.x
open
nobody
modules (357)
5
2009-07-24
2009-07-24
Alex Hermann
No

After one record has failed to insert/update into the database, remaining records aren't tried.

The attached patch tries to insert/update the remaining records in the hashtable after a failure.

This patch surfaced bug #2824350 which led to a lot of failures due to duplicate keys.

Discussion

  • How to Repeat or Check the Error? Kindly explain the situation. I have tried in may ways it works fine in the version 1.5.2.

     
  • Alex Hermann
    Alex Hermann
    2009-11-10

    just let the DB update fail in some way. I got a duplicate key error somehow.

    The patch makes sure the remaining entries in the hash table are committed to the DB even after one record failed.

     
  • You can commit the patch - I was waiting for you to test if svn access works ok.

    Daniel