#16039: syncdb with --database option fails -------------------------------------+------------------------------------- Reporter: yedpodtrzitko | Owner: nobody Type: Bug | Status: new Component: Database layer | Version: 1.4 (models, ORM) | Resolution: Severity: Release blocker | Triage Stage: Design Keywords: | decision needed Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by charettes): In the case of multi-tenancy it can be quite useful to have both tables on another database or schema. Given a postgresql setup you can have a middleware that `SET search_path TO specific_client_schema` on a specific connection to a database with some specific `ContentType` and `Permission`. However I think that it's a really specific use case and both aaugustin's proposals make sense. I slightly prefer the first proposal since it doesn't introduce special cases that one might not expect. -- Ticket URL: <https://code.djangoproject.com/ticket/16039#comment:28> Django <https://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 django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.