#13565: Using syncdb with Oracle using synonyms causes ORA-00955.
---------------------------------------------------+------------------------
Reporter: [email protected] | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: | Keywords: oracle
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by ikelly):
* has_patch: 0 => 1
* needs_tests: 0 => 1
* stage: Unreviewed => Design decision needed
Comment:
The patch that I just uploaded fixes this issue by allowing the
introspection layer to recognize views and synonyms as existing tables,
which is probably the right way to go about it. However, this also breaks
commands like reset and sqlclear since Django now tries to drop those
tables automatically and fails. That makes me question whether this is
really something we want to do.
Comparing the behavior of the other backends, sqlite3 does the same thing
as oracle -- syncdb fails with an error if a defined model is implemented
as a view. Mysql runs syncdb successfully but fails on reset or sqlclear.
I didn't test postgresql because it doesn't seem to be correctly installed
on our test server just now.
Ultimately, I think that marking the affected models as unmanaged should
not be viewed as a "workaround" in this circumstance, but as the correct
thing to do.
--
Ticket URL: <http://code.djangoproject.com/ticket/13565#comment:5>
Django <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.
