#4140: [boulder-oracle]: manage.py syncdb fails with ORA-06552
------------------------------------------+---------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component:
django-admin.py
Version: other branch | Resolution:
Keywords: oracle | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------------+---------------------------------
Changes (by bouldersprinters):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
In your LogMessage model, the first column is named "timestamp". This is
an Oracle reserved keyword (we've often seen columns named "date" cause
the same problem). Renaming it and the references to it in that module
fixes the problem.
Unfortunately, Oracle will gladly create the table for you even with an
illegal column name that you won't be able to SELECT on. Then when trying
to compile the trigger referencing that table, it will bomb with "ORA-
06553: PLS-320: the declaration of the type of this expression is
incomplete or malformed," an utterly unhelpful error message.
This is brain-damaged Oracle behavior we can't fix, but we could perhaps
put in a check somewhere for SQL reserved words as column names so that
the problem is flagged earlier, with an informative message.
--
Ticket URL: <http://code.djangoproject.com/ticket/4140#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
