From 28bdeb6d3e016cccd713dd9d48e48f37faec447d Mon Sep 17 00:00:00 2001 From: epriestley Date: Wed, 20 Feb 2013 12:18:41 -0800 Subject: [PATCH] Document `YYYYMMDD.name.ext` format for SQL patches Summary: This isn't currently documented anywhere. Test Plan: Read text Reviewers: kwadwon Reviewed By: kwadwon CC: aran Differential Revision: https://secure.phabricator.com/D4988 --- src/docs/developer/database.diviner | 1 + 1 file changed, 1 insertion(+) diff --git a/src/docs/developer/database.diviner b/src/docs/developer/database.diviner index 59a49d852e..8ad4e349f3 100644 --- a/src/docs/developer/database.diviner +++ b/src/docs/developer/database.diviner @@ -145,6 +145,7 @@ There are three simple steps to update the schema: # Create a `.sql` file in `resources/sql/patches/`. This file should: - Contain the approprate MySQL commands to update the schema. + - Be named as `YYYYMMDD.patchname.ext`. For example, `20130217.example.sql`. - Use `${NAMESPACE}` rather than `phabricator` for database names. - Use `COLLATE utf8_bin` for any columns that are to be used as identifiers, such as PHID columns. Otherwise, use `COLLATE utf8_general_ci`.