From: | "Carlos Oliva" <CarlosO(at)pbsinet(dot)com> |
---|---|
To: | "Adrian Klaver" <adrian(dot)klaver(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Dynamic File Name for COPY TO in Stored Procedure |
Date: | 2012-02-23 17:33:56 |
Message-ID: | C34A4F8A078F5E4285EB8B10FF0DAF3101F6A032@pbsi-sbsxch.PosBus.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
That worked. Thank you Adrian
-----Original Message-----
From: Adrian Klaver [mailto:adrian(dot)klaver(at)gmail(dot)com]
Sent: Thursday, February 23, 2012 9:58 AM
To: pgsql-general(at)postgresql(dot)org
Cc: Carlos Oliva
Subject: Re: [GENERAL] Dynamic File Name for COPY TO in Stored Procedure
On Thursday, February 23, 2012 6:42:53 am Carlos Oliva wrote:
> Hi,
> What would it be the correct format for using a variable in a stored
> procedure that uses COPY TO?
>
> I have the current stored procedure:
> CREATE FUNCTION Table_To_File(text) RETURNS void AS $delimeter$
> COPY (SELECT * FROM table_to_xml('table', true, false, '')) TO '$1'
> WITH CSV QUOTE ' ';
> $delimeter$
> LANGUAGE SQL;
>
> When I run the stored procedure: psql -d <db name> -c "select
> Table_To_File('some_absolute_file_name')"; I get the error that I
must
> use absolute file names.
>
> When I replace TO '$1' with TO '/tmp/toto.xml', the stored procedure
> runs fine and creates the local file.
>
> I have tried several different ways to escape the $1 variable to no
> avail. At best, I get the same error.
You will need to switch to using plpgsql and its EXECUTE statement to
build the COPY
statement :
http://www.postgresql.org/docs/9.0/interactive/plpgsql-statements.html#P
LPGSQL-STATEMENTS-EXECUTING-DYN
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2012-02-23 18:15:34 | Re: Optimise PostgreSQL for fast testing |
Previous Message | Scott Marlowe | 2012-02-23 17:20:37 | Re: Optimise PostgreSQL for fast testing |