Re: Thinking about EAV database model for flexibility. How (in)compatible is it with the django model?

> Den 22/12/2014 kl. 11.27 skrev Felipe Faraggi <felipefaraggi@gmail.com>:
>
> I'd like to 're-open' this question to ask another (maybe) short one:
>
> Therefore, is django not very suitable for NOSQL databases like mongo or couch or others in general?
> Or is the problem specifically using RDBMS in a NoSQL manner?

I haven't used Django with NoSQL, so I can't answer that specific question. The Django wiki has a page on NoSQL: https://code.djangoproject.com/wiki/NoSqlSupport

Which "problem" you are referring to? If you mean using an EAV in Django then the problem is not in Django as such, but rather that an EAV usually ends up being a miserable way of storing your data, regardless of which software you choose to implement it with.

Erik

--
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+unsubscribe@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/7888B586-E853-4B5D-A325-34CF166CF1D2%40cederstrand.dk.
For more options, visit https://groups.google.com/d/optout.