| From: | Andrew Chernow <ac(at)esilo(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Bernd Helmle <mailings(at)oopsware(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: bytea vs. pg_dump |
| Date: | 2009-05-06 14:14:55 |
| Message-ID: | 4A019B5F.6080804@esilo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>>
>> another nit with base64 is that properly encoded data requires
>> newlines according to the standard.
>>
>
> er, no, not as I read rfc 3548 s 2.1.
>
> cheers
>
> andrew
>
>
Why does encode('my text', 'base64') include newlines in its output? I
think MIME requires text to be broken into 76 char lines but why does
encode do this?
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-05-06 14:19:31 | Re: bytea vs. pg_dump |
| Previous Message | Tom Lane | 2009-05-06 13:37:19 | Re: Patch to fix search_path defencies with pg_bench |