2012/1/2 Seif Lotfy <909...@bugs.launchpad.net>:
> Here is the deal... Deleting is not that trivial since some "event info"
> might have been there before we tried to insert such as the event
> interpretation. So either we just delete the event row from the events
> table or we do it how i did it...

In fact, deleting should be trivial, everything is handled by triggers
and cascading.

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

  Inserting event with two subjects with the same URI breaks the
  following event

Status in Zeitgeist Framework:
  In Progress

Bug description:
  By the way our database is structured, all subjects of a same event
  must have different URIs.

  However, this isn't currently being checked, with the effect that the
  first subject is inserted correctly, while the second subject triggers
  the "existing event" exception and rolls back the event ID. This has
  the effect that the next event to be inserted will incorrectly have
  the same event ID (thus its subjects are mixed into whatever got saved
  of the first event and all sorts of weirdness :P).

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~zeitgeist
Post to     : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp

Reply via email to