Re: Double newline bug with DBD::Pg: Where best to fix? - Mailing list pgsql-interfaces

From Bruce Momjian
Subject Re: Double newline bug with DBD::Pg: Where best to fix?
Date
Msg-id 200102281806.NAA05912@candle.pha.pa.us
Whole thread Raw
In response to Re: Double newline bug with DBD::Pg: Where best to fix?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Double newline bug with DBD::Pg: Where best to fix?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-interfaces
> > Tom Lane writes:
> > 
> > > That's all fine IMHO.  But this isn't:
> > >
> > > regression=# select 'a string
> > > regression'#
> > > regression'# with a newline';
> > >         ?column?
> > > -------------------------
> > >  a string
> > > with a newline
> > > (1 row)
> > 
> > Well, *somebody* once figured that he could optimize away whitespace...
> > Not so.  Here's a patch that gets this case right:
> 

Peter, I have thought about this some more.   Seems we either add the
'quote' check, or remove the optimizations completely.  Because we have
to change it one way or the other for 7.1, it seems we should just
remove the tests totally.  Neither of us understand why they are even in
the code.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-interfaces by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Double newline bug with DBD::Pg: Where best to fix?
Next
From: Tom Lane
Date:
Subject: Re: Double newline bug with DBD::Pg: Where best to fix?