On Tue, Nov 8, 2011 at 5:58 AM, Ric <riccardodivirgi...@gmail.com> wrote: > you say "is rarely a good idea", and that it is the only thing true. > > when, like my app, you need to handle document, real documents (like > invoice, ddt, quotations) and other stuffs, it's a good practice to > keep all in one table, separating only the things that you need to > query, and leave a non relational field to handle evreything else. > > read http://guide.couchdb.org/ there are a lot of ideas that are > simply brillant. > > one of this is the validation of the non relational data, and django > has got a fantastic framework to validate data, so it would be grat to > implement a custom non relational field that can be validated, and > it's stored in one place, because for some applications the best > design practice is to put all the data in one place, because the date > is simply non relational. > > django should be able to handle this kind of situation, and please > don't be arrogant. > > you don't like non relational data, but non relational db are growing, > and maybe there is a reason. > > the reason is that relational data not always is the best answer.
This is not in dispute. What is in dispute is that when you have non-relational data, you should be using a non-relational data store, not trying to stuff non-relational data into your relational store. Tom correctly summarized the argument against putting JSONField in trunk -- it's the wrong tool for the job. If you have non-relational data, you should be using a non-relational store. Alternatively, you should be exploiting the non-relational data structures inside a relational store (e.g., PostgreSQL's hstore). At a project level, Django has a responsibility to advocate for best practices. Using the wrong tool for the job isn't best practice. If you really do need a JSONField, Django gives you the abilty to add one yourself as an external dependency, and for my money, that's the right place for JSONField to live. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
