Bug #20447 for DBD-Pg: Different in getline function removing new lines

Thu Jul 13 14:52:08 2006 ianburrell [...] gmail.com - Ticket created

Subject:

Different in getline function removing new lines

The behavior of getline is different depending on if the old PQgetline or new PGgetCopyData functions are used. The old interface removed the "\n" at the end of the line. The new interface leaves the "\n" at the end. This is a regression between old versions of DBD::Pg. And will be different when old versions of libpq are used with DBD::Pg 1.49.

Thu Jul 13 17:32:39 2006 mschwern [...] cpan.org - Correspondence added

On Thu Jul 13 14:52:08 2006, ianburrell@gmail.com wrote: Show quoted text

> The behavior of getline is different depending on if the old PQgetline > or new PGgetCopyData functions are used. The old interface removed the > "\n" at the end of the line. The new interface leaves the "\n" at the

end. Show quoted text

> > This is a regression between old versions of DBD::Pg. And will be > different when old versions of libpq are used with DBD::Pg 1.49.

To make it clear, we like the new interface where it leaves the "\n" on the end. It the fact that the interface changed which is the problem. At the very least DBD::Pg->pg_getline should behave the same no matter what internal pg function it uses.

Thu Jul 13 17:32:43 2006 The RT System itself - Status changed from 'new' to 'open'

Tue Jan 08 14:45:17 2008 greg [...] turnstep.com - Correspondence added

FWIW, DBD::Pg will no longer compile against 7.3 or earlier libraries, so PQgetCopyData will be the standard. Agreed that we should have been more careful in the transition.

Mon Feb 11 10:14:39 2008 greg [...] turnstep.com - Fixed in 2.0.0 added

Mon Feb 11 10:14:40 2008 greg [...] turnstep.com - Correspondence added

2.0.0 has the new API in place.

Mon Feb 11 10:16:22 2008 greg [...] turnstep.com - Status changed from 'open' to 'resolved'