#6148: Add generic support for database schemas
-------------------------------------+-------------------------------------
Reporter: ikelly | Owner: akaariai
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: oracle postgresql | Needs documentation: 1
mysql schemas | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Walkman):
Replying to [comment:156 pombredanne]:
> Also, what do you think of the approach in:
https://github.com/bernardopires/django-tenant-schemas
Setting search path in PostgreSQL is a very common technique in case of
multi-tenant applications, a lot of Rails people do it also, but that
wouldn't work either in SQLite, nor in MySQL which Django have to support.
Also, that project is not capable of handling cross-schema references,
which is the most important feature of a true multi-tenant application
IMO.
--
Ticket URL: <https://code.djangoproject.com/ticket/6148#comment:157>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.2c24374489d0317687eb2f757e799612%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
