From 77a69bc57eb6fb1b66fb76eafd6318f06ae4e295 Mon Sep 17 00:00:00 2001 From: zYne Date: Wed, 30 Aug 2006 22:40:03 +0000 Subject: [PATCH] Docs for autoincrement and composite identifiers --- ...Getting started - Record identifiers - Autoincremented.php | 2 ++ .../docs/Getting started - Record identifiers - Composite.php | 4 ++++ 2 files changed, 6 insertions(+) diff --git a/manual/docs/Getting started - Record identifiers - Autoincremented.php b/manual/docs/Getting started - Record identifiers - Autoincremented.php index e69de29bb..2c107e319 100644 --- a/manual/docs/Getting started - Record identifiers - Autoincremented.php +++ b/manual/docs/Getting started - Record identifiers - Autoincremented.php @@ -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: diff --git a/manual/docs/Getting started - Record identifiers - Composite.php b/manual/docs/Getting started - Record identifiers - Composite.php index e69de29bb..37f636a03 100644 --- a/manual/docs/Getting started - Record identifiers - Composite.php +++ b/manual/docs/Getting started - Record identifiers - Composite.php @@ -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. +

+Due to this fact your doctrine-based system will scale better if it has autoincremented primary key even for association tables.