RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2025-02-13 02:39:25 +03:00
Code Issues Projects Releases Wiki Activity

Merge pull request #6805 from yesdevnull/patch-1

Browse Source 
[Docs] Corrected NamingStrategy demo code to match example
This commit is contained in:
Michael Moravec 2017-12-12 04:30:01 +01:00 committed by GitHub
commit a352c214a0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/en/reference/namingstrategy.rst
View File

@ -97,7 +97,7 @@ a naming strategy for database tables and columns.
Implementing a naming strategy Implementing a naming strategy
------------------------------- -------------------------------
If you have database naming standards, like all table names should be prefixed If you have database naming standards, like all table names should be prefixed
by the application prefix, all column names should be upper case, you can easily by the application prefix, all column names should be lower case, you can easily
achieve such standards by implementing a naming strategy. achieve such standards by implementing a naming strategy.
You need to create a class which implements ``Doctrine\ORM\Mapping\NamingStrategy``. You need to create a class which implements ``Doctrine\ORM\Mapping\NamingStrategy``.