Hi all !
I want to use Django on an existing database where every user have his
own table.
I want to be able to define one "generic" model for every user and
choose db_table at runtime
there is "table_a" and "table_b" which is a sub-table of "table_a"
Database looks like this :
For user "100" I h
On Fri, Nov 26, 2010 at 2:34 PM, Seb wrote:
> Hi all !
>
> I want to use Django on an existing database where every user have his
> own table.
> I want to be able to define one "generic" model for every user and
> choose db_table at runtime
> there is "table_a" and "table_b" which is a sub-table o
On Nov 26, 2:34 pm, Seb wrote:
> Hi all !
>
> I want to use Django on an existing database where every user have his
> own table.
> Any idea ?
Yes: don't do this. Really, really, don't do this.
There's absolutely no reason for each user to have their own table. It
breaks not only Django's ORM,
> First off, this is a stupid database design. Do you really create new
> tables in your DB each time you add a user? Mental.
yes you're right and what I said was just a example ;)
In the real app, there's no per user table but per company
the database is used by many different companies and eac
On Fri, Nov 26, 2010 at 4:33 PM, Sebastien Ramage
wrote:
>
>
>> First off, this is a stupid database design. Do you really create new
>> tables in your DB each time you add a user? Mental.
>
> yes you're right and what I said was just a example ;)
> In the real app, there's no per user table but p
5 matches
Mail list logo
