archive/phabricator
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Explain why we store table names in lower-case

Browse Source 
Test Plan: Read it.

Reviewers: epriestley

Reviewed By: epriestley

CC: aran, Korvin

Differential Revision: https://secure.phabricator.com/D4607
This commit is contained in:
vrana
2013-01-23 16:59:14 -08:00
parent c9870b12ae
commit 451ea2f958
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/docs/developer/database.diviner
View File

@@ -45,7 +45,9 @@ DarkConsole (see @{article:Using DarkConsole}) and other places.
The exception is tables which share the same schema over different databases The exception is tables which share the same schema over different databases
such as `edge`. such as `edge`.
We use lower-case table names with words separated by underscores. We use lower-case table names with words separated by underscores. The reason is
that MySQL can be configured (with `lower_case_table_names`) to lower-case the
table names anyway.
= Column Names = = Column Names =
@@ -152,7 +154,7 @@ add your patch to @{method@phabricator:PhabricatorBuiltinPatchList::getPatches}.
# Run `bin/storage/upgrade`. # Run `bin/storage/upgrade`.
It is also possible to create more complex patches in PHP for data migration It is also possible to create more complex patches in PHP for data migration
(due to schema changes or otherwise.) However, the schema changes themselves (due to schema changes or otherwise.) However, the schema changes themselves
should be done in separate `.sql` files. Order can be guaranteed by editing should be done in separate `.sql` files. Order can be guaranteed by editing
`src/infrastructure/storage/patch/PhabricatorBuiltinPatchList.php` `src/infrastructure/storage/patch/PhabricatorBuiltinPatchList.php`
appropriately. appropriately.