Rajesh Dhawan schrieb: > You mention above that it was important to you to have multiple > instances of the app models in your DB. Can you explain the reason > behind this so people can see if there's a way to do this better? > > > One company holds several sub companies. There are people who have access to several sub companies, but some are restricted to only one. The app contains a big full text index. If a small company searches, they only want to search in the small index. With the sites framework, the result is the same, but it will be slower.
Django's current admin interface does not support row based access control. You can access/deny only at model/table level. But why not use several projects? Because I want to use some parts together (auth). I think there are three solutions. site framework: One table: Good, if you want to publish some parts on two site. several projects which use one app: Several databases. Completely separated. my solution: One DB, several tables. Thomas -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
