| From: | "David Wilson" <david(dot)t(dot)wilson(at)gmail(dot)com> |
|---|---|
| To: | "Klint Gore" <kgore4(at)une(dot)edu(dot)au> |
| Cc: | pgsql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: copy ... from stdin csv; and bytea |
| Date: | 2008-07-28 05:39:56 |
| Message-ID: | e7f9235d0807272239x55a6f4adia8b3d5a3c5dc749b@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jul 28, 2008 at 1:24 AM, Klint Gore <kgore4(at)une(dot)edu(dot)au> wrote:
> Try just a single \
>
> e.g.
> "ge.xls","application/vnd.ms-excel",71168,"\320\317\021\340\241[snip]
Thanks- I did try that, and it at least gave the expected output from
select, but is there a way to verify that it's actually handling it
correctly rather than simply storing the sequence of characters? I'm
not certain how to check the actual byte width of a column within a
row, and I'd *really* rather not be storing 4 bytes for every 1 in the
binary if I can avoid it- this column is already going to be doubling
field width; quadrupling it would give me space headaches I really
don't want to deal with. :)
--
- David T. Wilson
david(dot)t(dot)wilson(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Klint Gore | 2008-07-28 06:10:44 | Re: copy ... from stdin csv; and bytea |
| Previous Message | Klint Gore | 2008-07-28 05:24:57 | Re: copy ... from stdin csv; and bytea |