Thread: using copy from in function

using copy from in function

From
"Yura Gal"
Date:
I'm trying to automate import data using CORY FROM. For this purpose I
wrote plpgsql function. As my postgres works on windows vista I need
to use E'' syntax for path-to-file. This syntax works fine in SQL
queries like:
COPY table FROM E'path_to_file_with_double_backslashes';

Following query works fine too:
COPY table FROM $$path_to_file_with_single_backslashes$$;

However I can't figure it out how to use file_path variable as this
code throw error while compilation:

CREATE OR REPLACE FUNCTION func (inout _chrom varchar) RETURNS varchar AS
$body$
DECLARE _chrom ALIAS FOR $1; _file TEXT;
BEGIN _file := $$c:\folder1\folder2\$$ || _chrom || '.txt'; RAISE NOTICE 'Filename is -> %', _file; COPY table (column)
FROM_file CSV HEADER;
 
 statements;

EXCEPTION
WHEN bad_copy_file_format THEN_chrom := 'badformat';
WHEN io_error THEN_chrom := 'ioerr';
WHEN undefined_file THEN_chrom := 'unfile';RETURN;
END;
$body$
LANGUAGE 'plpgsql' ;

ERROR: syntax error in query at or near "$1" at character 35
QUERY:   COPY table (column) FROM $1 CSV HEADER
CONTEXT: SQL statement in PL/PgSQL function "func" near line 7

Is there any tricks to solve this problem? I suspect that something
wrong with quotation but can not find out a mistake.

PS. Postgres server version is 8.3


Re: using copy from in function

From
"Osvaldo Kussama"
Date:
2008/3/4, Yura Gal <yuragal@gmail.com>:
> I'm trying to automate import data using CORY FROM. For this purpose I
>  wrote plpgsql function. As my postgres works on windows vista I need
>  to use E'' syntax for path-to-file. This syntax works fine in SQL
>  queries like:
>  COPY table FROM E'path_to_file_with_double_backslashes';
>
>  Following query works fine too:
>  COPY table FROM $$path_to_file_with_single_backslashes$$;
>
>  However I can't figure it out how to use file_path variable as this
>  code throw error while compilation:
>
>  CREATE OR REPLACE FUNCTION func (inout _chrom varchar) RETURNS varchar AS
>  $body$
>  DECLARE
>   _chrom ALIAS FOR $1;
>   _file TEXT;
>  BEGIN
>   _file := $$c:\folder1\folder2\$$ || _chrom || '.txt';
>   RAISE NOTICE 'Filename is -> %', _file;
>   COPY table (column) FROM _file CSV HEADER;
>
>   statements;
>
>  EXCEPTION
>  WHEN bad_copy_file_format THEN
>         _chrom := 'badformat';
>  WHEN io_error THEN
>         _chrom := 'ioerr';
>  WHEN undefined_file THEN
>         _chrom := 'unfile';
>         RETURN;
>  END;
>  $body$
>  LANGUAGE 'plpgsql' ;
>
>  ERROR: syntax error in query at or near "$1" at character 35
>  QUERY:   COPY table (column) FROM $1 CSV HEADER
>  CONTEXT: SQL statement in PL/PgSQL function "func" near line 7
>
>  Is there any tricks to solve this problem? I suspect that something
>  wrong with quotation but can not find out a mistake.
>
>  PS. Postgres server version is 8.3
>
>


Try:
EXECUTE 'COPY table (column) FROM ' || _file || 'CSV HEADER;';

Osvaldo


Re: using copy from in function

From
Steve Midgley
Date:
At 03:20 AM 3/5/2008, pgsql-sql-owner@postgresql.org wrote:
>Date: Wed, 5 Mar 2008 01:51:19 +0300
>From: "Yura Gal" <yuragal@gmail.com>
>To: pgsql-sql@postgresql.org
>Subject: using copy from in function
>Message-ID: 
><3b6c69d80803041451i6d4d358dk53e9b789bfacd40e@mail.gmail.com>
>
>I'm trying to automate import data using CORY FROM. For this purpose I
>wrote plpgsql function. As my postgres works on windows vista I need
>to use E'' syntax for path-to-file. This syntax works fine in SQL
>queries like:
>COPY table FROM E'path_to_file_with_double_backslashes';
[snip]
>   _file := $$c:\folder1\folder2\$$ || _chrom || '.txt';

Hi,

I'm not sure if this is related, but I have had terrible trouble using 
"\" marks for paths in WinXP.. I have found surprisingly that "/" work 
and don't cause any parsing problems. Also, I believe that if you use 
syntax like:

'/folder1/folder2/' || _chrom || '.txt'

(i.e. leaving off the "c:" part too), you may find that everything just 
works a little cleaner / fewer unexpected surprises.

Like I said, I don't know if this is your issue (and Vista), but it's 
been my experience with WinXP and file paths in Postgresql.

Best,

Steve