RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2025-01-29 19:41:45 +03:00
Code Issues Projects Releases Wiki Activity

Docs for autoincrement and composite identifiers

Browse Source
This commit is contained in:
zYne 2006-08-30 22:40:03 +00:00
parent 713a49a075
commit 77a69bc57e
2 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
manual/docs/Getting started - Record identifiers - Autoincremented.php
View File

@ -0,0 +1,2 @@
Autoincrement primary key is the most basic identifier and its usage is strongly encouraged. Sometimes you may want to use some other name than 'id'
for your autoinc primary key. It can be specified as follows:

4
manual/docs/Getting started - Record identifiers - Composite.php
View File

@ -0,0 +1,4 @@
Composite primary key can be used efficiently in association tables (tables that connect two components together). It is not recommended
to use composite primary keys in anywhere else as Doctrine does not support mapping relations on multiple columns.
<br \><br \>
Due to this fact your doctrine-based system will scale better if it has autoincremented primary key even for association tables.