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. non relational data it's a tool, and in some situation it's the best practice. for me the first step it's to create a JsonField, than we can use validators to let the developers validate non relational data. On 7 Nov, 12:45, Tom Evans <tevans...@googlemail.com> wrote: > On Sat, Nov 5, 2011 at 11:48 AM, Ric <riccardodivirgi...@gmail.com> wrote: > > this is my proposition to have custom data inside a model field > > > a json data field, the code is simple as this, and it works with > > lastest django release > > The problem with something like this is that it is rarely a good idea > to stick opaque data into the database that cannot then be queried > upon. You may have a very good reason for doing this, but most of the > time that it happens it ends up being a bad design choice. > > Adding this to core would suggest that bad design choices are a-ok in > Django, which is why I expect many people are -0/-1 on this. If I had > a vote, I'd be -1. > > Cheers > > Tom -- 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.
