Google Groups Home
Help | Sign in
Message from discussion Support for a binary storage field?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
Jacob Kaplan-Moss  
View profile
 More options Mar 26 2007, 11:03 am
From: "Jacob Kaplan-Moss" <jacob.kaplanm...@gmail.com>
Date: Mon, 26 Mar 2007 10:03:38 -0500
Local: Mon, Mar 26 2007 11:03 am
Subject: Re: Support for a binary storage field?
On 3/26/07, Simon G. <d...@simon.net.nz> 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


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2008 Google