On Mon, 2007-03-26 at 10:03 -0500, Jacob Kaplan-Moss wrote: > -1 on allowing File/ImageField to be stored in the database. That's > bad design 99% of the time, and will needlessly complicate file upload > code. > If people want to do it themselves, it's pretty easy to create a DBFile model with name and data members, so leaving it out of core doesn't preclude people from doing it if they're set on the idea. (I just want a BinaryField; I'll take it however I can get it.)
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
