mirror of
https://we.phorge.it/source/phorge.git
synced 2024-11-26 00:32:42 +01:00
Fixing of the typos
Test Plan: doitlive Reviewers: epriestley, chad Reviewed By: epriestley, chad Subscribers: cspeckmim, Korvin Differential Revision: https://secure.phabricator.com/D17727
This commit is contained in:
parent
f880000eb0
commit
305966e748
3 changed files with 17 additions and 17 deletions
|
@ -10,7 +10,7 @@ Database System
|
||||||
Phabricator uses MySQL or another MySQL-compatible database (like MariaDB
|
Phabricator uses MySQL or another MySQL-compatible database (like MariaDB
|
||||||
or Amazon RDS).
|
or Amazon RDS).
|
||||||
|
|
||||||
Phabricator the InnoDB table engine. The only exception is the
|
Phabricator uses the InnoDB table engine. The only exception is the
|
||||||
`search_documentfield` table which uses MyISAM because MySQL doesn't support
|
`search_documentfield` table which uses MyISAM because MySQL doesn't support
|
||||||
fulltext search in InnoDB (recent versions do, but we haven't added support
|
fulltext search in InnoDB (recent versions do, but we haven't added support
|
||||||
yet).
|
yet).
|
||||||
|
@ -102,7 +102,7 @@ An example of such usage can be found in column
|
||||||
Primary Keys
|
Primary Keys
|
||||||
============
|
============
|
||||||
|
|
||||||
Most tables have auto-increment column named `id`. Adding an ID column is
|
Most tables have an auto-increment column named `id`. Adding an ID column is
|
||||||
appropriate for most tables (even tables that have another natural unique key),
|
appropriate for most tables (even tables that have another natural unique key),
|
||||||
as it improves consistency and makes it easier to perform generic operations
|
as it improves consistency and makes it easier to perform generic operations
|
||||||
on objects.
|
on objects.
|
||||||
|
@ -134,12 +134,12 @@ eventually, but there isn't a strong case for them at the present time.
|
||||||
PHIDs
|
PHIDs
|
||||||
=====
|
=====
|
||||||
|
|
||||||
Each globally referencable object in Phabricator has its associated PHID
|
Each globally referencable object in Phabricator has an associated PHID
|
||||||
("Phabricator ID") which serves as a global identifier, similar to a GUID.
|
("Phabricator ID") which serves as a global identifier, similar to a GUID.
|
||||||
We use PHIDs for referencing data in different databases.
|
We use PHIDs for referencing data in different databases.
|
||||||
|
|
||||||
We use both autoincrementing IDs and global PHIDs because each is useful in
|
We use both auto-incrementing IDs and global PHIDs because each is useful in
|
||||||
different contexts. Autoincrementing IDs are meaningfully ordered and allow
|
different contexts. Auto-incrementing IDs are meaningfully ordered and allow
|
||||||
us to construct short, human-readable object names (like `D2258`) and URIs.
|
us to construct short, human-readable object names (like `D2258`) and URIs.
|
||||||
Global PHIDs allow us to represent relationships between different types of
|
Global PHIDs allow us to represent relationships between different types of
|
||||||
objects in a homogeneous way.
|
objects in a homogeneous way.
|
||||||
|
@ -154,7 +154,7 @@ Transactions
|
||||||
============
|
============
|
||||||
|
|
||||||
Transactional code should be written using transactions. Example of such code is
|
Transactional code should be written using transactions. Example of such code is
|
||||||
inserting multiple records where one doesn't make sense without the other or
|
inserting multiple records where one doesn't make sense without the other, or
|
||||||
selecting data later used for update. See chapter in @{class:LiskDAO}.
|
selecting data later used for update. See chapter in @{class:LiskDAO}.
|
||||||
|
|
||||||
Advanced Features
|
Advanced Features
|
||||||
|
@ -195,12 +195,12 @@ set names:
|
||||||
|
|
||||||
| Variable | Meaning | Notes |
|
| Variable | Meaning | Notes |
|
||||||
|---|---|---|
|
|---|---|---|
|
||||||
| {$NAMESPACE} | Storage Namespace | Defaults to `phabricator` |
|
| `{$NAMESPACE}` | Storage Namespace | Defaults to `phabricator` |
|
||||||
| {$CHARSET} | Default Charset | Mostly used to specify table charset |
|
| `{$CHARSET}` | Default Charset | Mostly used to specify table charset |
|
||||||
| {$COLLATE_TEXT} | Text Collation | For most text (case-sensitive) |
|
| `{$COLLATE_TEXT}` | Text Collation | For most text (case-sensitive) |
|
||||||
| {$COLLATE_SORT} | Sort Collation | For sortable text (case-insensitive) |
|
| `{$COLLATE_SORT}` | Sort Collation | For sortable text (case-insensitive) |
|
||||||
| {$CHARSET_FULLTEXT} | Fulltext Charset | Specify explicitly for fulltext |
|
| `{$CHARSET_FULLTEXT}` | Fulltext Charset | Specify explicitly for fulltext |
|
||||||
| {$COLLATE_FULLTEXT} | Fulltext Collate | Specify explicitly for fulltext |
|
| `{$COLLATE_FULLTEXT}` | Fulltext Collate | Specify explicitly for fulltext |
|
||||||
|
|
||||||
|
|
||||||
**Test your patch**. Run `bin/storage upgrade` to test your patch.
|
**Test your patch**. Run `bin/storage upgrade` to test your patch.
|
||||||
|
|
|
@ -52,9 +52,9 @@ problems.
|
||||||
I joined the new Dev Tools team around February 2010 and took over Diffcamp. I
|
I joined the new Dev Tools team around February 2010 and took over Diffcamp. I
|
||||||
renamed it to Differential, moved it to a new Alite-based infrastructure with
|
renamed it to Differential, moved it to a new Alite-based infrastructure with
|
||||||
Javelin, and started making it somewhat less terrible. I eventually wrote
|
Javelin, and started making it somewhat less terrible. I eventually wrote
|
||||||
Diffusion and build Herald to replace a very difficult-to-use predecessor. These
|
Diffusion and built Herald to replace a very difficult-to-use predecessor. These
|
||||||
tools were less negatively received than the older versions. By December 2010 I
|
tools were less negatively received than the older versions. By December 2010 I
|
||||||
started open sourcing them; Haste became //Celerity// and Alite became
|
started open sourcing them; Haste became //Celerity// and Alite became
|
||||||
//Aphront//. I wrote Maniphest to track open issues with the project in January
|
//Aphront//. I wrote Maniphest to track open issues with the project in January
|
||||||
or February and we open sourced Phabricator in late April, shortly after I left
|
or February, left Facebook in April, and shortly after, we open sourced
|
||||||
Facebook.
|
Phabricator.
|
||||||
|
|
|
@ -134,5 +134,5 @@ query escaping system the rest of the application does.
|
||||||
|
|
||||||
Hopefully, whatever language you're writing in has good query libraries that
|
Hopefully, whatever language you're writing in has good query libraries that
|
||||||
can handle escaping for you. If so, use them. If you're using PHP and don't have
|
can handle escaping for you. If so, use them. If you're using PHP and don't have
|
||||||
a solution in place yet, the Phabricator implementation of qsprintf() is similar
|
a solution in place yet, the Phabricator implementation of `qsprintf()` is
|
||||||
to Facebook's system and was successful there.
|
similar to Facebook's system and was successful there.
|
||||||
|
|
Loading…
Reference in a new issue