Inconsistent data in event_view
Bug #580601 reported by
Markus Korn
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
To post a comment you must log in.
> 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.