NYCPHP Meetup

NYPHP.org

[nycphp-talk] DB Schema for storing revision history?

csnyder chsnyder at gmail.com
Thu Jun 28 14:54:36 EDT 2007


On 6/27/07, David Krings <ramons at gmx.net> wrote:
> Steve Francia wrote:
> > The version table would have the document_id, content and the mod_date
> > and author_id.
>
> I am by no means a database expert, but why would one want to store
> guaranteed to be static data in a table such as the content. That
> content will never ever change. I agree with all other parts of your
> proposal, but recommend to store only a file path to each version of the
> file to keep the static bloat as small as possible.

Be careful of over-simplifying so much that it becomes complex. By
storing important data outside of the database, you have created a
situation in which two different sets of data need to be backed up,
migrated to different servers, configured into applications, etc.

Databases are extremely useful for keeping related data together.

-- 
Chris Snyder
http://chxo.com/



More information about the talk mailing list