zeitgeist team mailing list archive

[Seif Lotfy <909708@xxxxxxxxxxxxxxxxxx>]

Option 3 makes most sense but IMHO it would be good to inform the developer
of the error

On Thu, Dec 29, 2011 at 3:13 PM, Siegfried Gevatter
<rainct@xxxxxxxxxx>wrote:

> Options:
>
> 1. Add a check to see if there are any duplicate subjects. If so, rollback
> all insertions done to that point and throw an exception.
> 2. Just ignore the second and later subjects with the same URI and keep
> going.
> 3. DELETE what was inserted of that particular event and return 0 for it
> (but insert all other events).
>
> --
> You received this bug notification because you are subscribed to The
> Zeitgeist Project.
> https://bugs.launchpad.net/bugs/909708
>
> Title:
>  Inserting event with two subjects with the same URI breaks the
>  following event
>
> Status in Zeitgeist Framework:
>  Confirmed
>
> 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:
> https://bugs.launchpad.net/zeitgeist/+bug/909708/+subscriptions
>

-- 
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/909708

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

Status in Zeitgeist Framework:
  Confirmed

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:
https://bugs.launchpad.net/zeitgeist/+bug/909708/+subscriptions