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

Hi All, Since no one has mentioned it, I'd also like to draw attention to Django's postgres hstore support, which is a dict-like data structure coming in Django 1.8: https://docs.djangoproject.com/en/dev/ref/contrib/postgres/fields/#hstorefield Collin On Tuesday, December 23, 2014 3:19:43 AM

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

You guys are really active on this board! Thanks so much for your time once again. My question has been answered at its fullest. On Monday, December 22, 2014 11:00:46 PM UTC+1, Jamie Lawrence wrote: > > Well, Django, in the role of an ORM, is necessarily pretty coupled to SQL. > I know people

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

Well, Django, in the role of an ORM, is necessarily pretty coupled to SQL. I know people have been toying with nosql databases with Django; I don't know much about those efforts. EAV intentionally defeats the intended use of RDBMSes by ignoring normalization and data typing, thus (among other

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 : > > 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

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

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? Because if using NOSQL, the whole model system would be

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

Thanks for your responses Jamie and Erik, We've since reconsidered and will in fact, be creating a standard relational structure. Again, thanks for your input and feedback On Tuesday, December 16, 2014 2:18:12 AM UTC+1, Jamie Lawrence wrote: > > Just to add to Erik's very good advice on

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

Just to add to Erik's very good advice on (not) using EAV, another thing to keep in mind is that the downsides of EAV tend to manifest after your app is hosting a substantial amount of data, at which point the exercise of sanitizing it in order to port it to a saner model can be *excruciating*.

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

> Den 15/12/2014 kl. 14.42 skrev Felipe Faraggi : > > After a little digging I discovered this is called the Entity-attribute-value > model or EAV. And I am currently setting up a project in django in which my > data is very variable because we will be opening up to

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

Hello everybody. I am very new to django and I come from a wordpress background (yes, yes I know) and I really like their wp_*meta model. After a little digging I discovered this is called the Entity-attribute-value model or EAV