From: | Leonardo M(dot) Ramé <l(dot)rame(at)griensu(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | PostgreSql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Parsing COPY ... WITH BINARY |
Date: | 2013-02-01 19:34:39 |
Message-ID: | 20130201193439.GC4318@leonardo-laptop |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2013-01-31 17:38:26 -0600, Merlin Moncure wrote:
> On Thu, Jan 31, 2013 at 8:47 AM, Leonardo M. Ramé <l(dot)rame(at)griensu(dot)com> wrote:
> > I'm using this:
> >
> > COPY( select field1, field2, field3 from table ) TO 'C://Program Files/PostgreSql//8.4//data//output.dat' WITH BINARY
> >
> > To export some fields to a file, one of them is a ByteA field. Now, I
> > need to read the file with a custom made program.
> >
> > How can I parse this file?
> >
> > BTW: I cannot export as CSV, because the binary data is modified when I
> > do that.
>
> this type of thing is probably better handled with libpq based C
> application if you're willing to write one. all this is assuming you
> don't want to decode your bytea from encoded format such as hex. why
> do you specifically need to dump in binary?
>
> merlin
>
I need to dump in binary because in the dump I have bytea fields. I know
PostgreSql escapes binary data, but I don't want to regenerate it to
"see" in my program.
Anyway, I solved the issue by creating a FreePascal program for parsing
the file, based on the info from here:
http://www.postgresql.org/docs/current/static/sql-copy.html#AEN66736
--
Leonardo M. Ramé
Medical IT - Griensu S.A.
Av. Colón 636 - Piso 8 Of. A
X5000EPT -- Córdoba
Tel.: +54(351)4246924 +54(351)4247788 +54(351)4247979 int. 19
Cel.: +54 9 351 6629292
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2013-02-02 01:21:54 | Re: trouble with upgrade from 9.0 (many schemas and tables) |
Previous Message | Sahagian, David | 2013-02-01 17:50:48 | ATET, could it be made "more concurrent" ? |