From: Dan Lyke <danlyke@flutterby.com>
To: pgsql-interfaces@postgresql.org
Cc: Peter Eisentraut <peter_e@gmx.net>
Subject: Re: Double newline bug with DBD::Pg: Where best to fix?
Date: Tue, 27 Feb 2001 12:39:47 -0800 (PST)
Message-ID: <15004.4243.481906.138327@wynand.flutterby.com> (raw)
In-Reply-To: <9388.983305623@sss.pgh.pa.us>
References: <15003.65308.557357.318833@wynand.flutterby.com>
<9351.983305318@sss.pgh.pa.us>
<9388.983305623@sss.pgh.pa.us>
Tom Lane writes:
> On closer look, there is no leading-space issue. Psql is formatting the
> column with a leading space as it usually does, and the newline-space
> in the string is just being echoed. Compare:
Yep, you're completely right.
And in fact a little more testing (and pulling my head out of my butt)
indicates that there's no problem at all with DBD::Pg, it's all with
psql and the fact that I was using $dbh->quote to write a script which
got piped into psql.
Dang it, that's twice I've made a stupid foul-up on my end with
potential PostgreSQL bugs.
Anyway, we've at least established that there's a bug in psql. I can
patch my one script to work around it, if I get into the psql source
I'll try to drop a fix on y'all, although given my recent attention to
detail that might not be a good idea...
Dan
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-interfaces@postgresql.org
Cc: danlyke@flutterby.com, peter_e@gmx.net
Subject: Re: Double newline bug with DBD::Pg: Where best to fix?
In-Reply-To: <15004.4243.481906.138327@wynand.flutterby.com>
* 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