Database Development w/ SVN

Hi all,

This is more of a best or general practice question than anything
else. How do you manage/version external database schema and static
data changes in an SVN environment?

For example, r5 adds a new table, and also the code to do all the
standard CRUD operations. How is it communicated that the schema then
needs to be added to the testing database, etc? This would also apply
to any sort of 'static data' (ie tax rates and scales, etc) that are
standard across all systems.

Our in-house VCS simply tied the schema deltas and upgrade procedures
to the work order, so we could track where they came from. It also
allow for the tester to know what needed to be applied to their
testing environment. When building the release, all upgrade procedures
for completed work orders were extracted, then a final delta between
our master dictionary, and the current live was generated.

Another option is to introduce a Rails migrations concept (each
delta/upgrade procedure would have a unique number for the version,
running 'ant upgrade' (or equivalent) would apply all outstanding
items.

Is there a generally accepted practice for managing the database
data/schema in an SVN environment?

Regards,

---
Daniel Becroft
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2416279
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].