On Mon, Nov 7, 2011 at 11:48 PM, Torsten Bronger <bron...@physik.rwth-aachen.de> wrote: > > While I appreciate that Django core is supposed to enforce good > design practices, one must be careful with that if some practice may > have valid use cases. You cannot prevent the user from shooting in > the foot anyway. > > While we make extensive use of the relational model in our project, > I remembered to have a couple of JSON fields (though we don't have a > field class them them so far), so I skimmed through our code to see > why we did this. >
And so do I - the main point here is that we have both successfully loaded the gun and aimed it at our foot without this field existing in core. I think it's important to have that distinction between things you can do and things you should do, in order to make you think "should I really be doing this". 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.
