From: Sebastian P. Luque <spluque@gmail.com>
To: pgsql-sql@postgresql.org
Subject: Re: \copy multiline
References: <87r4ndnlfn.fsf@kolob.subpolar.dyndns.org>
	<1354181617.2124.17.camel@localhost.localdomain>
Mail-Followup-To: pgsql-sql@postgresql.org
Date: Thu, 29 Nov 2012 09:35:13 -0600
In-Reply-To: <1354181617.2124.17.camel@localhost.localdomain> (Guillaume
	Lelarge's message of "Thu, 29 Nov 2012 10:33:37 +0100")
Message-ID: <877gp4o21a.fsf@kolob.subpolar.dyndns.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Organization: University of Manitoba
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

On Thu, 29 Nov 2012 10:33:37 +0100,
Guillaume Lelarge <guillaume@lelarge.info> wrote:

> On Wed, 2012-11-28 at 21:21 -0600, Seb wrote:
>> Hi,

>> I use \copy to output tables into CSV files:

>> \copy (SELECT ...) TO 'a.csv' CSV

>> but for long and complex SELECT statements, it is cumbersome and
>> confusing to write everything in a single line, and multiline
>> statements don't seem to be accepted.  Is there an alternative, or am
>> I missing an continuation-character/option/variable that would allow
>> multiline statements in this case?


> A simple way to workaround this issue is to create a view with your
> query and use the view in the \copy meta-command of psql. Of course,
> it means you need to have the permission to create views in the
> database.

Thanks.  Someone also suggested creating a temporary view, which helps
keep the schema sane and clean.

Cheers,

-- 
Seb


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql