The DB is the same, only the API changes to make everything clearer
(and export more information). See the mail I've send you.

Also I don't understand what's the problem here - the problem
described in this bug is completely unrelated to the changes. I
believe there's just a misunderstanding again because of vocabulary;
eg. "does not mean seperated in terms of class inheritance" - events
aren't classes in the implementation * so why do we have to talk this

*  (well, in my branch there are Event and Item classes, but that's

Siegfried-Angel Gevatter Pujals (RainCT)
Free Software Developer       363DEAE3

origin should be a property of events, not items
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.

Status in Zeitgeist Engine: Triaged

Bug description:
Both and our current 
implementation have "origin" as a property of items, but this makes no sense, 
as the origin can be different for every event and should as such be a property 
of it. (Further, to improve disk space usage we should save the actual value of 
it in the "uri" table).

I'm filling this bug so that we don't remember to fix it, but please let's 
ignore it until we get the basic event/item separation stuff merged - most 
important stuff first.

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to