I'm relatively new to the Django world and I'm just starting on a new project that may be right up the frameworks ally. But there's one thing I'm a little iffy on after reading the documentation.
I'm attempting to write an app that will allow for management of a "parts" database that will allow for parts to be added with a couple auto-generation features. The parts database I wish to edit is maintained by a separate program called Altium, so the structure of the database is pretty rigid, and the way it's set up is it creates Tables for classes of parts (so all capacitors that are of size 0805 will be found in the table, CAPS_0805). These tables are frequently created as we run across a new class of part. So the names of the tables that this app would be editing are far from static. It would appear using the Models system of Django the tables which I could setup all of Djangos magic on are pretty rigidly named (aka, I can't just use some variable name to represent the table). The only solution I see right off to this would be to create a chron job that would edit the models file for me after checking the database (automatically creating models for each of the tables). I feel like this is a hack to something that shouldn't really need one. Also, then I think I would have to use dictionaries if I wanted to treat the table names as variables in the program which looks ugly. (The user will for example select which table the part needs to go in from a drop down menu). Any insight here would be much appreciated. Thanks, Matthias Welsh. -- 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.
