mirror of
https://we.phorge.it/source/phorge.git
synced 2024-11-26 08:42:41 +01:00
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
This commit is contained in:
parent
41b9752ba8
commit
28bdeb6d3e
1 changed files with 1 additions and 0 deletions
|
@ -145,6 +145,7 @@ There are three simple steps to update the schema:
|
||||||
|
|
||||||
# Create a `.sql` file in `resources/sql/patches/`. This file should:
|
# Create a `.sql` file in `resources/sql/patches/`. This file should:
|
||||||
- Contain the approprate MySQL commands to update the schema.
|
- 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 `${NAMESPACE}` rather than `phabricator` for database names.
|
||||||
- Use `COLLATE utf8_bin` for any columns that are to be used as identifiers,
|
- Use `COLLATE utf8_bin` for any columns that are to be used as identifiers,
|
||||||
such as PHID columns. Otherwise, use `COLLATE utf8_general_ci`.
|
such as PHID columns. Otherwise, use `COLLATE utf8_general_ci`.
|
||||||
|
|
Loading…
Reference in a new issue