#132 Archived alerts unvisible in archive db

closed-fixed
Nerveup
Database (41)
5
2006-02-15
2006-02-13
Anonymous
No

After archived some alerts few times they don't show up
in archive db until I rebuild alert cache.

Reproduce:
Move/Copy to archive db alert with cid for example 1111.
Go to archive db, you see that alert.
Than go back to alerts db and move/copy another alert
with cid for example 55, go to archive db and youll see
there only alert with cid 111.

/* if the CID in the cache < the CID in the event table
* then there are events which have NOT been added to
the cache
*/

But this will not work for archive db because in any
moment alert with lesser cid can appear in archivedb.
Only complate delete/update alerts cache does the job.
I have no idea how to fix this except replace "update
alert cache" with "rebuild alert cache", but this will
hit performance for heavy archive db's ;]

Discussion

  • Nerveup

    Nerveup - 2006-02-13
    • labels: --> Database
    • assigned_to: nobody --> nerveup
    • status: open --> open-accepted
     
  • Nerveup

    Nerveup - 2006-02-13

    Logged In: YES
    user_id=1429350

    mkay.
    What if we update alert cache for given alert right after we
    copy it to archive db!?

    Would it be accaptable by BASE design?

     
  • Nerveup

    Nerveup - 2006-02-15
    • status: open-accepted --> closed-fixed
     
  • Nerveup

    Nerveup - 2006-02-15

    Logged In: YES
    user_id=1429350

    Fixed into cvs.
    Now we update alert cache for archived alert right after it
    is coppied to archive db.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks