Versioning code in db

[eluser]Glen Swinfield[/eluser]
My reasons for suggesting an xml file were not just about storage, the database option (that Expression Engine uses for its template revisions I think) requires quite a few DB transactions to perform a fairly simple task - and you have to deal with the possibilty of multiple people editing the same content at the same time. This can all be easily resolved by using a file and in the end you have a single document that provides a rolling log of all activity and the current version. This can be easily archived/un archived as required/ transform with xslt and so on.

I am not suggesting that you should or could not use a database, just that sometimes databases seem to be the default solution to problems that can be answered in other ways. Databases provide functionality to quickly order, search and query volumes of data - but this doesn't seem to be the primary purpose of your system.

That said - xwero's DB solution seems like the most practical/scalable.