From: Steve Midgley <public@misuse.org>
To: pgsql-sql@postgresql.org
Subject: Re: COPY FROM query
Date: Mon, 12 Feb 2007 12:24:13 -0800
Message-ID: <20070212203449.33FE99FB2E8@postgresql.org> (raw)
In-Reply-To: <20070212190914.1F8439FB616@postgresql.org>
References: <20070212190914.1F8439FB616@postgresql.org>
Hi,
For what it's worth, WindowsXP (at least) seems to currently support
forward slashes at the OS level, so this Postgres behavior isn't as odd
as it might seem. If you enclose your paths with double quote (")
marks, Windows will even accept Unix style paths for some instructions
on the command line:
dir "/temp"
Feeding Windows API calls with forward slashes seems to work with
everything I've tried so far, so using them in Postgres seems perfectly
smart, and reasonable..
Hope that helps,
Steve
At 11:03 AM 2/12/2007, pgsql-sql-owner@postgresql.org wrote:
>Date: Mon, 12 Feb 2007 09:09:08 +0900
>From: Paul Lambert <paul.lambert@autoledgers.com.au>
>To: Joe <dev@freedomcircle.net>
>Cc: pgsql-sql@postgresql.org
>Subject: Re: COPY FROM query.
>Message-ID: <45CFB024.7040207@autoledgers.com.au>
>
>Joe wrote:
> > Hi Paul,
> >
> > On Mon, 2007-02-12 at 08:19 +0900, Paul Lambert wrote:
> >> I'm attempting to copy from a table into a file using a select
> query
> >> inside the copy.
> >>
> >> The following is my command:
> >>
> >> COPY (SELECT DISTINCT ON (dealer_id,appraisal_id) * FROM
> >> appraisals_temp) TO 'c:\autodrs_appraisal_new.txt' WITH DELIMITER
> AS '^'
> >> CSV HEADER;
> >>
> >> I get the following returned:
> >>
> >> WARNING: nonstandard use of escape in a string literal
> >> LINE 1: ...ealer_id,appraisal_id) * FROM appraisals_temp) TO
> 'C:\autodr...
> >> ^
> >> HINT: Use the escape string syntax for escapes, e.g., E'\r\n'.
> >>
> >> ERROR: relative path not allowed for COPY to file
> >> SQL state: 42602
> >>
> >>
> >> (The caret character is pointing to the M in FROM)
> >
> > I believe that on Windows you need to use double backslashes, i.e.,
> 'c:\
> > \autodrs_appraisal_new.txt', although the regular slash may also
> work,
> > i.e., 'c:/autodrs_appraisal_new.txt'.
> >
> > Joe
> >
> >
> > ---------------------------(end of
> broadcast)---------------------------
> > TIP 5: don't forget to increase your free space map settings
> >
> >
>
>If this is the case, it is strange that the first copy statement works
>
>as that is also only using a single backslash.
>
>Having said that, if I switch it to a forward slash it works without
>error... odd, given that weenblows standard is backslash.
>
>Thanks for the help though.
>
>--
>Paul Lambert
>Database Administrator
>AutoLedgers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: public@misuse.org
Subject: Re: COPY FROM query
In-Reply-To: <20070212203449.33FE99FB2E8@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox