On 3/26/07, Simon G. <[EMAIL PROTECTED]> wrote: > So - if we do want a BinaryField we could use #2417 and make it > suitable for larger binary stores (e.g. the VARBINARY used for MySQL > has a max length of 255 bytes - perfect for the small bin. chunks > wanted in #2417, but not for larger data), and then hook it up to > Image/FileFields for #652. > > An alternate solution is to check in #2417 for small binary chunks, > and then hold 652 back until we decide if we want a LargeBinaryField > for large binary chunks suitable for file uploads.
+1 on having a BinaryField. I'd actually like to see BinaryField be the "larger" binary field, and have a SmallBinaryField alongside for databases with those types. -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. Jacob --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
