On Fri, May 20, 2011 at 7:55 AM, Michael Giarlo
wrote:
> I suspect we would go with #3
definitely #3. it's called multi-tenancy, and it's a mess to add to
an existing application, much better to design from the start.
for the most part, it means most of your tables will need a 'tenant'
foreign
Hi,
My department has two customers who have identical needs, currently served by
separate applications. They both need an app w/ a public side and an
administrative side, and we had hoped to make use of the built-in Django admin
interface for the latter. We're wondering how to model this i
2 matches
Mail list logo
