Re: Console output with libpq

From: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Console output with libpq
Date: 2014-05-31 03:13:24
Message-ID: 1401506004684-5805644.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

alpha_one_x86 wrote
> Hello,
>
>> You're barking up the wrong tree
> I don't understand. Wrong mailling list?

Yes, English phrases can be so fun.

This particular one means that the approach or area of your search is not
one that is causing the problem or likely to yield a solution.
Specifically, those PQset... functions are not the source of your problem
nor usable for solving it. More broadly it isn't even a libpq problem at
all.

Imagine two trees with a cat in one of them. Now imagine a dog barking at
the tree the cat isn't in. That dog is barking up the wrong tree if it is
attempting to bark at the cat.

David J.

--
View this message in context: http://postgresql.1045698.n5.nabble.com/Console-output-with-libpq-tp5805610p5805644.html
Sent from the PostgreSQL - interfaces mailing list archive at Nabble.com.

In response to

Browse pgsql-interfaces by date

  From Date Subject
Next Message Greg Sabino Mullane 2014-06-02 17:23:07 DBD::Pg 3.3.0 released (driver for Postgres)
Previous Message alpha_one_x86 2014-05-30 21:36:57 Re: Console output with libpq