Hi all, I was quite surprised that I couldn't find a way to override table names for an application's models on a per-deployment basis (i.e. in settings.py or some other project/site specific file instead of modifying the models.py file of the app itself)
Although I admit all of these are rare, I think the scenarios of (a) having table_name naming conflicts between apps or (b) working with legacy data in existing tables or (c) renaming an app while wanting to keep the data, would justify the "external" specification of an application's table names. In my case I had to rename an application for external reasons, and would like to continue using the existing data in all my deployments. Renaming all the tables in the databases would be quite tedious. The only related thing I could find is http://code.djangoproject.com/ticket/891 which wouldn't help in above scenarios anyway. What do you think? Is there something I've overlooked? Best, Flo -- You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en.
