I don't think the option 3 (recommended) by the presented is the best way forward. It is error prone, risky, customers data is mixed together, does not allow to have customer specific deviation / logic.
Great presentation thank you indeed. I note that ForeignKey statements need to be adjusted with django_multitenant ... what about ManyToMany statements?
Hey, Everything is good, but can you please share any demo project.
I don't think the option 3 (recommended) by the presented is the best way forward. It is error prone, risky, customers data is mixed together, does not allow to have customer specific deviation / logic.
I guess Option 2 is better when compared with 3.
Very clear and informative presentation. Thanks for sharing.
Great presentation thank you indeed. I note that ForeignKey statements need to be adjusted with django_multitenant ... what about ManyToMany statements?
Precise and informative. Thanks.
very informative presentation.And can we use it with Mysql ??
Yes
Since Django abstracts the DB layer this will work with any Django supported DB
Tq, I have doubt. How can we use json data for tenants instead of tenant model which is declared in settings (TENANT_MODEL)
Nicely explained, thanks
It's possible to add 2 different subdomain for same tenant??