Hi,
2. The second approach would be to have a database table for each of the users (probably no more than a 1000). I've read django has something in the lines of inspectdb, which actually checks which fields are there and produces the model for you. This could be useful but I think maybe I should store the fields this particular user has created and somehow dinamically tell django, hey, we also have this fields in this model. Is this possible? I know it's generally bad to have different tables for each user, but considering this scenario, how would you guys rate this method, would it be ok to have one table for each user?
Its not really the functional aspect that burdens me but rather to understand why on Earth a web site would need to store individual data on a per-user basis, unless for fascists tracking/monitoring reasons of your visitors.. As for this reason alone I'd decline this for political reasons. (-1)
The model that requires custom fields is for example Person. They might want a custom field to store address, blood type, or any other thing.
Whatever. ;-)
MANY THANKS in advance! Have a nice sunday! Bernardo Pires
cheers, Etienne -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
