From ab75fd4786563c4c178aa1164c96c826d0a88aa6 Mon Sep 17 00:00:00 2001 From: Ian Kelly Date: Thu, 28 Jan 2010 22:14:38 +0000 Subject: [PATCH] [1.1.X] Fixed #4140: Documented the ORA-06552 error that can occur when a keyword is used as a field name in the Oracle notes. Backport of r12346 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.1.X@12347 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/databases.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index a2f4e981ea..8563e8de93 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -593,6 +593,14 @@ Oracle imposes a name length limit of 30 characters. To accommodate this, the backend truncates database identifiers to fit, replacing the final four characters of the truncated name with a repeatable MD5 hash value. +When running syncdb, an ``ORA-06552`` error may be encountered if +certain Oracle keywords are used as the name of a model field or the +value of a ``db_column`` option. Django quotes all identifiers used +in queries to prevent most such problems, but this error can still +occur when an Oracle datatype is used as a column name. In +particular, take care to avoid using the names ``date``, +``timestamp``, ``number`` or ``float`` as a field name. + NULL and empty strings ----------------------