[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN v(+) database versioning question

From: Stefan Hett <stefan_at_egosoft.com>
Date: Thu, 31 Mar 2016 12:02:45 +0200

Hi Vit,
> Hello,
>
> may I ask a question: what would be the best way to achieve this with
> SVN:
>
> Database versioning scripts shall be (1) numbered (due to DBmaintain)
> and (2) incremental.
>
> ad 1) When a developer commits a script, I should get the next higher
> number
> than the last committed script. E.g. 045_customers.SQL, 046_orders.SQL
> etc
>
> ad 2) Scripts, which are once committed, should be immutable --
> developers
> should not be able to change them. They can only add new scripts.
>
> Many thanks in advance,
> V. Prochazka
Both should be achievable using pre-commit hooks. You can add a check to
ensure consecutive numbering of your SQL-script files as well as
preventing any modifications to committed files.

-- 
Regards,
Stefan Hett
Received on 2016-03-31 12:02:56 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.