I'm currently working on an app for browsing and visualizing time-series data. Each point of time-series data may be a mix of Strings, Floats, and Ints. In my current design, I have a separate model for each of my data types, and I have been writing a new view for each one. In other words, my app is strongly coupled to the structure of the models. *Ideally*, my app would use some sort of generic abstraction of a time-series model such that adding new types of data is a simple settings.py configuration, and the views for browse/visualize would be free.
I see a few possible avenues to accomplish this. None seems clearly better than any other. My database is MySQL. Any feedback is helpful! 1. Use django-mutant (or equivalent) to make new models on the fly. However I would really only need to make models at initialization time, not at runtime. 2. Instead of a column for each dimension of the data, use a Blob or Text type for headers and one for data (a hack for variable-length data. makes intelligent queries nearly impossible) 3. Forget about pluggability and continue developing under the assumption that this app will never leave "in-house" This is a deliberately vague question since it is about a vague topic: abstraction. I can provide more details about my specific use case, but that seems to defeat the purpose of writing a generic app. Thank you, RLange -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/7bdd3478-a4ce-43d8-a91e-f8220c05a2ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
