#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 |
---------------------------------------------------+------------------------
Comment (by dragonpaw):
Replying to [comment:5 ikelly]:
> 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.
Maybe the best solution is to have the existence of a managed table as a
synonym be a clearly unsupported combination with a proper error message
for it, instead of the 'object exists' one you get now. Something like:
Error: Table xxxxxx already exists as a synonym, but is set as
managed. Either remove the synonym, or set 'managed = False' in the Meta.
--
Ticket URL: <http://code.djangoproject.com/ticket/13565#comment:6>
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.
