On Wed, Mar 6, 2013 at 1:38 AM, Ian <ian.g.kelly@gmail.com> wrote:
> In the meanwhile, the commonly used workaround for this is to include the
> schema in the db_table declaration like so:
The other workaround which is mentioned in the ticket I linked but
which I completely neglected to include in my reply, and which I
heartily recommend, is to create private synonyms within the Django
schema to the tables in other schemas. This works perfectly fine
(it's what we do at my work) and allows you to avoid having
ugly-looking db_table names or having to patch Django. The only real
issue again is that syncdb will not recognize the synonyms and will
try to create the tables if run.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment