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.
