On Apr 9, 2009, at 12:20 PM, Steve Holden wrote:
PostgreSQL strongly encourages you to store text as encoded columns.
Because emails lack an encoding it turns out this is a most
inconvenient
storage type for it. Sadly BLOBs are such a pain in PostgreSQL that
it's
easier to store the message
(email-sig dropped, as I didn't see Steve Holden's message there)
At 12:20 -0400 04/09/2009, Steve Holden wrote:
>Tony Nelson wrote:
...
>> If you need the data from the message, by all means extract it and store it
>> in whatever form is useful to the purpose of the database. If you need the
>>
Tony Nelson wrote:
> (email-sig added)
>
> At 08:07 -0400 04/09/2009, Steve Holden wrote:
>> Barry Warsaw wrote:
> ...
>>> This is an interesting question, and something I'm struggling with for
>>> the email package for 3.x. It turns out to be pretty convenient to have
>>> both a bytes and a str
(email-sig added)
At 08:07 -0400 04/09/2009, Steve Holden wrote:
>Barry Warsaw wrote:
...
>> This is an interesting question, and something I'm struggling with for
>> the email package for 3.x. It turns out to be pretty convenient to have
>> both a bytes and a string API, both for input and outp
