Following up on my previous post: http://groups.google.com/group/django-users/browse_thread/thread/20ff5190a4b46d05/68b5fe2d6770fd26?lnk=gst&q=class+definitions#68b5fe2d6770fd26
I can more precisely articulate what it is I'm trying to do now, and would like to once again ask for advice on the best way to proceed. Say I have a class called 'RecordType'. this class has a 'name' charfield and a one-to-many relationship with... ...'RecordField'. RecordFields has a 'name' charfield and a 'type' charfield. What would actually get entered in the 'type' charfield is a field type, like 'integer', 'text', etc. So each instance of 'RecordType' has a name, and multiple fields attached to it. I'd like to turn each instance of 'RecordType' into it's own class (named after RecordType.name), using the instances of 'RecordField' as the fields for the class.. I'd also like to add any new fields detected (represented by new instances of 'RecordField') The database-driven example living at http://code.djangoproject.com/wiki/DynamicModels is somewhat close to what I need, however the syncdb caveats are, well, caveats. As for why I prefer the idea of db>models.py>db as opposed to db>db, correct me if I'm wrong, but... I was thinking about how most future apps and functionality for updating the database will probably be geared towards manually edited models.py files, and, following the DRY principle, instead of getting any new functionality to play nice with db-represented models, I think it would be better to just have it (future functionality) use something it already expects (models.py files) The larger question here is: Is there an existing way to (properly, in terms of Django) instantiate/ update tables and their columns using the rows of another table? The more specific question is: Is there an existing way to massage db rows into classes and fields in a models.py file? If no to both, what are your thoughts on the best way to handle making that models.py file using db data? I was thinking of using some kind of intermediary, like XML, for example (there are some neat things I can think of that using an intermediary would allow for) -D. Py --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
