Hi Lavanya, > In the project I am currently working on, we create hundred's of > tables during runtime.
Have you considered re-architecting your application in a way that doesn't require creation of tables at runtime? I am curious of your usecase scenarios that resulted in this design choice. > > Django book says every table requires a model class to be created to > access the table. Unfortunately, this solution doesn't fit our > project. > > Creating model class for each and every db table is mandatory? Is > there any alternative? Well, it's only mandatory if you want to take advantage of Django's ORM to access your tables. Otherwise, it's not required for you to create a model class for each table. -Rajesh D --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
