From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | Edmund Bacon <ebacon(at)onesystem(dot)com> |
Cc: | pgsql-interfaces <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | Re: ECPG and COPY TO STDOUT |
Date: | 2004-04-03 16:27:35 |
Message-ID: | 20040403162735.GA8682@1 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
On Thu, Apr 01, 2004 at 12:22:44PM -0700, Edmund Bacon wrote:
> If I use COPY TO STDOUT in an ECPG program, where does the output go?
Nowhere, it's discarded.
> What I'm trying to do is to dump a table's data, and have the resulting
> file owned by the application user rather than the dba user.
ecpg gets PGRES_COPY_OUT as a result from the execution and just calls
PQendcopy() without reading the data. The same happens btw with
PGRES_COPY_IN. It's working like this since the get-go in the sources I
inherited from Linux Tolke. I guess we could add this to the todo list
as a feature request.
Patches are welcome of course. :-)
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
From | Date | Subject | |
---|---|---|---|
Next Message | Jason E. Stewart | 2004-04-04 15:42:23 | View permissions |
Previous Message | Adriaan Joubert | 2004-04-03 05:35:45 | Bug in translation of DEALLOCATE PREPARE |