On Thu, Feb 21, 2008 at 8:57 PM, Luke Mason <lmason_at_oasisasset.com.au>
wrote:
> Hi All,
>
> We have certain files that can only be applied once to an
> environment. Mostly database table scripts like create table, alter table,
> some inserts that fill with default data, etc. Using PVCS, we use promotion
> groups to manage this. If/when we move to subversion, how would we manage
> this?
>
> Also, we manually list all the files required for a change in a tracking
> system. This allows us to set an apply order - you want to create the table
> before you attempt to insert data into it, or maybe alter it before you
> update it. If SVN doesn't require us to keep the list of files, because the
> atomic commits are an intrinisic changeset, (something we're looking forward
> to) how do we maintain this apply order? DO we have to keep the manual
> list of files, but just the database changes, not every file in the change?
>
Subversion certainly does not have any of these that you are asking. These
kind of things should be not be done by a source version control system
anyway.
You should write scripts to accomplish these. For example, your script can
check if the database exists and then accordingly invoke the script if it
does not.
Thanks,
-Hari
Received on 2008-02-22 07:24:48 CET