2009/11/19 Jason Smith :
> Zeitgeist Developers,
>
> There is an amazing amount of activity surrounding the happenings of
> Zeitgeist. Lots of excitement going on and obviously Zeitgeist will
> continue to be an important part of the linux experience in the coming
> years. Zeitgeist has not been wi
uhm not really
if u insert 50 events and all are the same do we want to get a list of 50
identical ids or just a list with one id in it?
This is a tough decision but i think the direction is pretty right. we shall
not skip other inserts just because one failed.
2009/11/19 Mikkel Kamstrup Erlandsen
Zeitgeist Developers,
There is an amazing amount of activity surrounding the happenings of
Zeitgeist. Lots of excitement going on and obviously Zeitgeist will
continue to be an important part of the linux experience in the coming
years. Zeitgeist has not been without issues, there have been two ma
For duplicate events this I think that Markus' proposal is OK. But do
we have any other error scenarios when inserting events? What is the
solution in this case then?
--
Dont' raise an exception when a duplicate event is detected
https://bugs.launchpad.net/bugs/485433
You received this bug notif
after thinking about it I think we should drop raising the KeyError.
Instead this we should return the id of the already existing event in the DB.
This way inserting 50 Events will always return a list of 50 ids.
--
Dont' raise an exception when a duplicate event is detected
https://bugs.launchp
Public bug reported:
19:52 thekorn: raising an exception on "Duplicate event detected" is
evil
19:53 thekorn: tell me how you want recent.py to work this way
19:53 RainCT, catch this exception
19:54 thekorn: doesn't help, if I'm sending 50 event and event 10 is
already there then events 11-5
6 matches
Mail list logo
