subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philipp Leusmann <>
Subject Re: One-time keyword substitution
Date Mon, 10 Jan 2011 15:34:01 GMT
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, while having to maintain a valid order to apply the SQL 
patches. My approach was to use the revision number as some kind of index.

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.


Am 10.01.2011 16:15, schrieb Thorsten Schöning:
> 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


Mit freundlichen Grüßen,

Philipp Leusmann
System Developer

Ebcot Business Solutions GmbH
Kreuzherrenstrasse 2
D-52062 Aachen

Telefon: +49 - (0)241 - 90 06 72 05
Fax:     +49 - (0)241 - 4 09 15 81

Reg.-Nr. HRB 116 74, Amtsgericht Aachen. Hauptsitz Aachen
Vertretungsberechtigte Geschäftsführer:
Andreas Hauser, Michael Kalinowski, Oliver Wolff

Diese E-Mail könnte vertrauliche und/oder rechtlich geschützte
Informationen enthalten. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die
unbefugte Weitergabe dieser E-Mail sind nicht gestattet.

View raw message