#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:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by anonymous):
Replying to [comment:1 kmtracey]:
> This sounds like a good use case for the model Meta
[http://docs.djangoproject.com/en/dev/ref/models/options/#managed
managed=False] option?
Yes, setting it as not managed is a viable work around. But it would be
nice if one didn't have to do that to a bunch of tables that really
already exist. Other DB backends are able to detect existing tables fine,
making this an Oracle-specific oddity.
Alternatively, just change syncdb to catch and ignore the ORA-00955 error
and continue on, as the error can only mean that the item already exists,
and syncdb is supposed to ignore existing tables.
--
Ticket URL: <http://code.djangoproject.com/ticket/13565#comment:2>
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.
