subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorsten Schöning <>
Subject Re: One-time keyword substitution
Date Mon, 10 Jan 2011 15:15:48 GMT
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:
> Changes for Rev. 124 :

Should this become some kind of changelog or is this supposed to be the
SQL to change your database to reflect the most current version? In
the latter case, I would suggest another approach: Don't put
everything in one file but create a directory like "updates" or else
and store every change needed to the database as one file with a
version number. Each file can then be documented on it's own. But you
don't get something like a changelog, in my opinion this should be
better generated directly from the log, and I wouldn't recommend using
svn version numbers, but like in applications something more abstract
that fits your needs.

We for example just number our database scheme like svn does with it's
content: We have version 1, 2 ... to n of our database, each version
has it's own update file as the changes needed to get from one version
to another and is documented using Doxygen/Javadoc-style syntax.

Mit freundlichen Grüßen,

Thorsten Schöning

Thorsten Schöning
AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig
Telefon: Potsdam: 0331-743881-0

AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam
Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow

View raw message