I am not sure why you would want "all companies bank accounts in different tables." Is it for security? to ensure that only appropriate people are able to view the records of any given company? There is the row-level-permissions branch, but I do not believe it has been maintained in a while so I rolled my own by implementing a very simple row-level access based on the 'organization' that a user belongs to. You may want to consider something like this. -r
On Jul 28, 1:47 pm, anna <[EMAIL PROTECTED]> wrote: > Hello my friends. > > I need your help in designing our new based application. > The goal is to build a kind of backoffice system, which helps to > organize all data of a specific company. > No problem with it. Build your models, data structures, input and > output 'screens'. > > But... > this application goes to a 'proxy' company, who's job is organize > other companies data. (Assume its an accounting firm, for example) > All models etc. are the same in each, but we expressly don't want to > store same data in same table (i mean all companies bank accounts are > in different tables) > We have to create new 'database' dynamically from a web based > interface seamlessly. > Did you solve similar problem already? > Prefixing tables, different databases or what? > > Thank you for any advice. > > Anna --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
