From 8376abb9d20ab694d7deb630ab916ff4e36d7695 Mon Sep 17 00:00:00 2001 From: VladimirMangos Date: Thu, 5 Feb 2009 22:59:39 +0300 Subject: [PATCH] [7231] Some info to sql updates commiters in slq/update/README --- sql/updates/README | 13 +++++++++++++ src/shared/revision_nr.h | 2 +- 2 files changed, 14 insertions(+), 1 deletion(-) diff --git a/sql/updates/README b/sql/updates/README index 61b8af96a..fd1a2d1c1 100644 --- a/sql/updates/README +++ b/sql/updates/README @@ -37,3 +37,16 @@ After appling this update DB compatiable with database that include this sql upd SQL update include special protection against multiply and wrong order SQL updates apply. So attempt apply sql update to more old DB without previous SQL update in list for targeted database or to DB with already applied this or later SQL update will generate error and not applied. + +=== For commiters ==== + +MaNGOS sources include special tool ( contrib/git_id ) for generation revision info +in commit notes and in src/shared/revision_nr.h file. It have option '-s' that let set +correct sql update names with revision number, generate sql update order guard queries, +and update version fields in mangos.sql/etc. For it use name sql updates in form +01_mangos_spell_chain.sql or 9999_01_mangos_spell_chain.sql (counter can be _01_, _02_, and etc, +dependent from sql updates amount in commit) and _not_ add to sql updates +guard queries. Include sql updates in commit. After commit adding to local repo call git_id +with -s option (and another, note: -s option not work propertly with -l option). Other steps +tool will do by self and apply changes to commit. After tool use commit with sql updates ready +to push. diff --git a/src/shared/revision_nr.h b/src/shared/revision_nr.h index 0d3bb9afb..d9e8e87e3 100644 --- a/src/shared/revision_nr.h +++ b/src/shared/revision_nr.h @@ -1,4 +1,4 @@ #ifndef __REVISION_NR_H__ #define __REVISION_NR_H__ - #define REVISION_NR "7230" + #define REVISION_NR "7231" #endif // __REVISION_NR_H__