I came up with the same conclusion. Em ter, 17 de mar de 2015 10:56, Django User <deva.seetha...@gmail.com> escreveu:
> yes, i did. however, none of those approaches look compelling for a > production system. > > > On Tuesday, March 17, 2015 at 6:06:11 PM UTC+5:30, Guilherme Leal wrote: > >> did you looked into some of these >> <http://stackoverflow.com/questions/7933596/django-dynamic-model-fields/7934577#7934577> >> aproaches? >> >> Em ter, 17 de mar de 2015 às 09:07, Guilherme Leal <leal...@gmail.com> >> escreveu: >> >>> I REALLY would appreciate some feature like this. If some >>> developer/engeneer has implemented something like it, please share your >>> knowledge. >>> >>> The first thing i would test, is to save the model in a .py file (i >>> think that saving the model might be important for the performance, since >>> the python interpreter will compile it and stuff), and in some way reload >>> de app (since the models are registered on the app during the >>> configuration step of the app). >>> >>> Not sure if this would work though... >>> >>> Em ter, 17 de mar de 2015 às 08:27, Django User <deva.se...@gmail.com> >>> escreveu: >>> >>> hello, >>>> we are working on an application where users can register new types of >>>> data streams through Django. so it requires a mechanism to create new >>>> tables (cassandra) on the fly. what is the best Djangoish way to implement >>>> such dynamic models? pls. let us know. thanks in advance. >>>> >>>> -- >>>> 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...@googlegroups.com. >>>> To post to this group, send email to django...@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/ms >>>> gid/django-users/59af92ca-940f-40a8-8518-34d33ccce00e%40goog >>>> legroups.com >>>> <https://groups.google.com/d/msgid/django-users/59af92ca-940f-40a8-8518-34d33ccce00e%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- > 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/8746285c-ce5d-4c01-8dc4-02c12fe299df%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/8746285c-ce5d-4c01-8dc4-02c12fe299df%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAOs3Lp6As0Hy3wkCTdpU8zGm6XCQKrU5diqV%2BwSDroaF8zHdXw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
