Inconsistent data in event_view

Bug #580601 reported by Markus Korn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zeitgeist Framework
Invalid
Undecided
Unassigned

Bug Description

While working on the wildcard implementation I had some hard time with our event_view view.
And I'm esp. wondering why event.actor and event.subj_mimetype are ids where fields like event.subj_origin is already JOINed to the actual string.

Is this on purpose? shouldn't be all fields (except *Interpretation and *Manifestation) be evaluated to strings instead of being an id? Or am I missing sth. which is very important (maybe wrt. performance)

Siegfried, Mikkel can you please explain this design to me.

Thanks,
Markus

Revision history for this message
Siegfried Gevatter (rainct) wrote : Re: [Bug 580601] [NEW] Inconsistent data in event_view

> Is this on purpose?
Yes.

There are only a few dozen actors and mimetypes, while there can be
any number of different origins. Actors and mimetypes are cached at
startup.

Revision history for this message
Seif Lotfy (seif) wrote :

I set this bug as invalid since Siegfried kinda gave a good explanation for the decision...
Feel free to change it back

Changed in zeitgeist:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.