You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the weblog Managing database updates

#5 Re: Managing database updates Posted by mvanbaak (80.126.xx.xx) on Sat 3 Feb 2007 at 09:39 We have 1 file with the original schema. After that everytime we have to patch the database we create a file called: YYYYmmddNN.sql (2007020300.sql would be the first database patch today) In a small settings table for our applications we also have a field called 'latest_patch' If there are files newer than this field content we apply all the new files to the database first time a user accesses the page/app. We have a script that first 'svn up' in the sql patches dir so we are sure the patches are applied before we 'svn up' the code so we know for sure we wont get sql errors because of missing fields. Hope this helps.

Username:	Anonymous
Title:
Your Comment:
Posting Format:	BBCode HTML Text Plain Text Textile

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account