Guten Tag Philipp Leusmann,
am Montag, 10. Januar 2011 um 16:34 schrieben Sie:
> Using separate files would be another approach, but it still has the
> problem of naming them properly to form a timeline without much effort
> to recognize the order for the deployer.
I don't think there is a simple
Hi Thorsten,
thanks for your answer. And as you already have guessed, the file shall
be used to contain al necessary changes to the database.
The current problem we have, is updating the patch file from
bugfix-branches and merging it into the trunk and also update it in the
trunk itself, whi
2011/1/10 Philipp Leusmann
> is there a way to have svn substitute a keyword only once and then leave it
> at the substituted value?
>
To get directly to your answer: No, Subversion doesn't do what you want.
There is a whole mess of debate on the value of RCS keywords in both
Subversion and oth
Guten Tag Philipp Leusmann,
am Montag, 10. Januar 2011 um 15:52 schrieben Sie:
> On commit, the file would change to
> Changes for Rev. 123:
> CREATE TABLE FOO;
> Changes for Rev. 124 :
> DROP * FROM FOO;
Should this become some kind of changelog or is this supposed to be the
SQL to change your
