So after playing around a bit i found out that the storage id of "net"
is incremented everytime i restart zeitgeist... still looking for more
clues but it is a hint that it might be

When a UNIQUE constraint violation occurs, the REPLACE algorithm deletes
pre-existing rows that are causing the constraint violation prior to
inserting or updating the current row and the command continues
executing normally.

Which means we should use use 2 statements instead of "INSERT OR

** Changed in: zeitgeist
       Status: Confirmed => Triaged

** Changed in: zeitgeist
   Importance: Undecided => High

You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.

  Storage monitor sets up weird storage ids

Status in Zeitgeist Framework:

Bug description:
  Seems like the storage monitor is giving out random ids or something that are 
not respected by the event
  I have several entries in my event table with storage_id 863 which however 
does not exist.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to