X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (neptune.hub.org [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP id 0191DD1B47C
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Sat, 20 Dec 2003 18:36:18 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 03787-08
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Sat, 20 Dec 2003 14:35:28 -0400 (AST)
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by svr1.postgresql.org (Postfix) with ESMTP id 7593CD1B42F
	for <pgsql-sql@postgresql.org>; Sat, 20 Dec 2003 14:35:27 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id hBKIZQ19017819;
	Sat, 20 Dec 2003 13:35:26 -0500 (EST)
To: "Matt Van Mater" <nutter_@hotmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: how to preserve \n in select statement 
In-reply-to: <BAY9-F42t0CI76rOJhK00098f93@hotmail.com> 
References: <BAY9-F42t0CI76rOJhK00098f93@hotmail.com>
Comments: In-reply-to "Matt Van Mater" <nutter_@hotmail.com>
	message dated "Sat, 20 Dec 2003 12:58:39 -0500"
Date: Sat, 20 Dec 2003 13:35:26 -0500
Message-ID: <17818.1071945326@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200312/138
X-Sequence-Number: 16304

"Matt Van Mater" <nutter_@hotmail.com> writes:
>> In particular, you have to separate data from SQL command if you want a
>> no-escape-processing behavior for data.

> right, I was looking for the alternate input methods that you allude to.  I 
> have been unable to find an example of exactly how to do this.

The best way at the moment is to use the parameterized-statement
features that are new in 7.4.  If using libpq, see PQexecParams()
and siblings.

			regards, tom lane