The is_active column, on tables tag, tag_obj and others, is for future use, to "unDo" friendly the drop and similar actions. To manage the valid states on this scenery: the state diagram below shows the "backup states" and the "current system states".
It generates an overhead on VIEWs and queries, because for final user the only important report is on the active ones.
In this issue we will discuss whether it is really necessary!
An alternative is to create "continuous backups" (instant/day/week/month)... Or we simply don't care about UnDo's.
The
is_activecolumn, on tablestag,tag_objand others, is for future use, to "unDo" friendly the drop and similar actions. To manage the valid states on this scenery: the state diagram below shows the "backup states" and the "current system states".It generates an overhead on VIEWs and queries, because for final user the only important report is on the active ones.
In this issue we will discuss whether it is really necessary!
An alternative is to create "continuous backups" (instant/day/week/month)... Or we simply don't care about UnDo's.