Re: How do I mark a file as run once?

Luke Mason 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?

This sounds like a job for make or some small scripts. This really
isn't in the scope of a source/version code control system.

-- 
Until later, Geoffrey
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org