| From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | Sim Zacks <sim(at)compulab(dot)co(dot)il>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: encoding confusion |
| Date: | 2008-06-11 18:06:01 |
| Message-ID: | 32F50C6D-492B-4500-A797-937152E5AA46@solfertje.student.utwente.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jun 11, 2008, at 9:03 AM, Richard Huxton wrote:
> Sim Zacks wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> The data in the longblob field might be text, which could be
>> causing the
>> confusion. For example, when I look at the data in the longblob
>> field, I
>> see /n for a newline and when I look at the bytea it is 012.
>
> That's right - newline is ASCII 10 (or 12 in octal).
Just from the top of my head, but aren't mail headers supposed to be
terminated by \r\n? In that case you're missing a byte 13 (or 015
octal) before the 012 byte. That could explain your missing line breaks.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4850140f927661409586227!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Dear | 2008-06-11 18:27:21 | Re: Unable to dump database using pg_dump |
| Previous Message | wenjing wu | 2008-06-11 17:33:21 | Fw: postgrepsql vacuum |