Problem, as you see is that Django is build for static models. So if you have a dynamic model, how would you construct (efficient) queries in your other views unless you know the structure of the data?

Well you kind of can't since there is no structure. Also, what purpose would such a models serve? I'm just trying to figure out what kind of system you're thinking to allow arbitrary ad-hoc models to be built? (What's the real world use case)


On 10.01.2017 13:09, Guilherme Leal wrote:
@Jani Tiainen
I really like Django ORM, and will make everything possible to keep it. I think that losing the ORM will make things harder in the big picture because it would make the logic built by the developers a lot more error prone and not "database agnostic" (at least as far as thedatabases backend suported by django go).

But thanks for the ideia, will certainly look for ArangoDB.

2017-01-10 5:58 GMT-02:00 Jani Tiainen <rede...@gmail.com <mailto:rede...@gmail.com>>:

    Hi,

    You're probably after EAV pattern (or anti-pattern depending who
    you ask).

    Implementing that in Django is relatively trivial, though with any
    kind of dynamics you'll going to loose most of the ORM goodies.

    This kind of leads to question that is Django ORM really needed
    for you at all? How about having NoSQL databases like ArangoDB to
    handle all the dynamics?


    On 04.01.2017 22:38, Guilherme Leal wrote:
    Is there a way to populate Django model cache on the fly?
    I was thinking about saving the model definition on some backend
    (database for instance) and loading as needed. This way we can
    basically build a custom admin interface for the model
    definitions, and load the models (through "type()" or something
    similar) into the cache "on the fly".

    Guilherme Leal
-- 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
    <mailto:django-users+unsubscr...@googlegroups.com>.
    To post to this group, send email to
    django-users@googlegroups.com <mailto:django-users@googlegroups.com>.
    Visit this group at https://groups.google.com/group/django-users
    <https://groups.google.com/group/django-users>.
    To view this discussion on the web visit
    
https://groups.google.com/d/msgid/django-users/CAOs3Lp7_R4RK%3DVconoQ1W6rzK8xYaiVJX-FHtyZ3Cxg4MmbOow%40mail.gmail.com
    
<https://groups.google.com/d/msgid/django-users/CAOs3Lp7_R4RK%3DVconoQ1W6rzK8xYaiVJX-FHtyZ3Cxg4MmbOow%40mail.gmail.com>.
    For more options, visit https://groups.google.com/d/optout
    <https://groups.google.com/d/optout>.

-- Jani Tiainen

-- 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
    <mailto:django-users+unsubscr...@googlegroups.com>.
    To post to this group, send email to django-users@googlegroups.com
    <mailto:django-users@googlegroups.com>.
    Visit this group at https://groups.google.com/group/django-users
    <https://groups.google.com/group/django-users>.
    To view this discussion on the web visit
    
https://groups.google.com/d/msgid/django-users/8a0abc75-a28d-f4a7-0d04-63f31afbde04%40gmail.com
    
<https://groups.google.com/d/msgid/django-users/8a0abc75-a28d-f4a7-0d04-63f31afbde04%40gmail.com?utm_medium=email&utm_source=footer>.


    For more options, visit https://groups.google.com/d/optout
    <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 <mailto:django-users+unsubscr...@googlegroups.com>. To post to this group, send email to django-users@googlegroups.com <mailto:django-users@googlegroups.com>.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAOs3Lp7H%2BQBBtZM4%3DGFG7ZYuDYVMQjX2GWm1GE4LXakAc9kF6Q%40mail.gmail.com <https://groups.google.com/d/msgid/django-users/CAOs3Lp7H%2BQBBtZM4%3DGFG7ZYuDYVMQjX2GWm1GE4LXakAc9kF6Q%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

--
Jani Tiainen

--
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/c4642a9e-53d9-833e-3d65-c5cc573060be%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to