← Back to team overview

zeitgeist team mailing list archive

optimization for usage of storage space

 

I know it sounds silly but...
We out log looks something like

event_id 1234567 event_actor, event_blabla then subject
alot of times the whole line is the same except for the timestamp
why not make log

event_id, event_timestamp, event_rest

event_rest will refer to another table with the remaining details of the
event and subjects since they could be repeated.
It wont break the API however it will add a new join but i think it could
help us out alot
so instead of a log with 13 columns full of ids
we will have one with 3 and another with 10
however that with 10 will not populate up very high

Please don't kill me its just a suggestion

Cheers
Seif

Follow ups