If you're using PostgreSQL you could try creating a schema for each tenant.
That's what django-tenancy <https://github.com/charettes/django-tenancy>does internally. You define which models are *tenant specific* by subclassing *TenantModel* and then you create instances of* Tenant* (or your the model you swapped it for) which creates the correct schema and tables. But this is getting a lot into the django-user land. I don't think Django should support it out-of-the-box Simon Le jeudi 11 avril 2013 02:32:35 UTC-4, jambunathan v.r a écrit : > > Right now, the django documentation advises against modifying the settings > dynamically as some caching is involved. > There are single tenant applications which need to talk to multiple > databases and the different databases that it needs to talk to might not be > known when the django server is started. This means that the django server > processes are different for different accounts, which is not a ideal > scalable scenario or the server processes needs to be restarted everytime a > new database is added. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
