Versioned articles database design
I am writing web application with content like articles. I want to keep
history of changes of each editation. What will be the best database
design to store such data?
Why am I asking: I have seen some projects (like wordpress), witch stores
everything to single table with column marking last version. But, is this
good solution, if I want to use fulltext index (PostgreSQL 9.1)? Wont be
indexed all data, regardless of information, if row is active last edited
version? I think this solution wont be good in any way for index size, row
count (slowest searching) specially after some time.
What would be better database design?
No comments:
Post a Comment