From 45118a2811175fb8afccc21459fce010c7a50460 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Steve=20M=C3=BCller?= Date: Mon, 25 Nov 2013 18:24:54 +0100 Subject: [PATCH] mention SQL Anywhere in basic mapping docs --- docs/en/reference/basic-mapping.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/en/reference/basic-mapping.rst b/docs/en/reference/basic-mapping.rst index 699df1d09..82b7cd02d 100644 --- a/docs/en/reference/basic-mapping.rst +++ b/docs/en/reference/basic-mapping.rst @@ -340,15 +340,16 @@ Here is the list of possible generation strategies: - ``AUTO`` (default): Tells Doctrine to pick the strategy that is preferred by the used database platform. The preferred strategies - are IDENTITY for MySQL, SQLite and MsSQL and SEQUENCE for Oracle - and PostgreSQL. This strategy provides full portability. + are IDENTITY for MySQL, SQLite, MsSQL and SQL Anywhere and SEQUENCE + for Oracle and PostgreSQL. This strategy provides full portability. - ``SEQUENCE``: Tells Doctrine to use a database sequence for ID generation. This strategy does currently not provide full - portability. Sequences are supported by Oracle and PostgreSql. + portability. Sequences are supported by Oracle, PostgreSql and + SQL Anywhere. - ``IDENTITY``: Tells Doctrine to use special identity columns in the database that generate a value on insertion of a row. This strategy does currently not provide full portability and is - supported by the following platforms: MySQL/SQLite + supported by the following platforms: MySQL/SQLite/SQL Anywhere (AUTO\_INCREMENT), MSSQL (IDENTITY) and PostgreSQL (SERIAL). - ``TABLE``: Tells Doctrine to use a separate table for ID generation. This strategy provides full portability. @@ -391,7 +392,7 @@ besides specifying the sequence's name: - + .. code-block:: yaml Message: