General discussions about libpqxx C++ interface to PostgreSQL

Curran Schiefelbein | 8 Jun 2007 02:40

Re: The libpqxx website is unreachable

BTW, link to old site is still given in documentation:
http://pqxx.org/devprojects/libpqxx/doc/2.6.9/html/Reference/
(see bottom of page)

Bart Samwel wrote:
 > Anyway, I suspect that you'll
> have to set a nonnoticer on the connection, something like:
> 
> conn.set_noticer std::auto_ptr<pqxx::noticer> (new pqxx::nonnoticer));

Thanks. I finally (<blush>) got around to trying this... funny thing is, 
I still get the printouts that begin with "+  INSERT INTO..." when the 
code runs.

When the connection object is created, its noticer is null, and then 
after the set_noticer call, the noticer is the NONnoticer I gave it. So 
the auto_ptr stuff should be working.

Actually, if the default value of m_Noticer's contents is null, then 
those "+  INSERT" printouts are definitely not caused by a noticer.

I've been grepping around for the right print statement in both pqxx and 
libpq, but haven't found it yet. Ideas?

--

-- 
Curran Schiefelbein

headers

Bart Samwel | 8 Jun 2007 20:20

Re: The libpqxx website is unreachable

Curran Schiefelbein wrote:
> BTW, link to old site is still given in documentation:
> http://pqxx.org/devprojects/libpqxx/doc/2.6.9/html/Reference/
> (see bottom of page)
> 
> 
> Bart Samwel wrote:
>  > Anyway, I suspect that you'll
>> have to set a nonnoticer on the connection, something like:
>>
>> conn.set_noticer std::auto_ptr<pqxx::noticer> (new pqxx::nonnoticer));
> 
> 
> Thanks. I finally (<blush>) got around to trying this... funny thing is, 
> I still get the printouts that begin with "+  INSERT INTO..." when the 
> code runs.
> 
> When the connection object is created, its noticer is null, and then 
> after the set_noticer call, the noticer is the NONnoticer I gave it. So 
> the auto_ptr stuff should be working.
> 
> Actually, if the default value of m_Noticer's contents is null, then 
> those "+  INSERT" printouts are definitely not caused by a noticer.
> 
> I've been grepping around for the right print statement in both pqxx and 
> libpq, but haven't found it yet. Ideas?

Nope, I'm puzzled! My grepping doesn't yield anything else... Perhaps 
libpq prints this stuff when it runs in some kind of debug mode? 
Otherwise I wouldn't know...

(Continue reading)

headers

Curran Schiefelbein | 8 Jun 2007 23:46

Re: The libpqxx website is unreachable

Bart Samwel wrote:
> Nope, I'm puzzled! My grepping doesn't yield anything else... Perhaps 
> libpq prints this stuff when it runs in some kind of debug mode? 
> Otherwise I wouldn't know...
> 
> Cheers,
> Bart
> 

It occurs regardless of whether you compile Debug or Release (both 
packages).

It doesn't matter that much. I'm the only one who looks at the output 
(so far). Thanks anyway.

--

-- 
Curran Schiefelbein

headers

Jeroen T. Vermeulen | 9 Jun 2007 15:45

Re: The libpqxx website is unreachable

On Sat, June 9, 2007 04:46, Curran Schiefelbein wrote:
> Bart Samwel wrote:
>> Nope, I'm puzzled! My grepping doesn't yield anything else... Perhaps
>> libpq prints this stuff when it runs in some kind of debug mode?
>> Otherwise I wouldn't know...

> It occurs regardless of whether you compile Debug or Release (both
> packages).

There's no printing of anything in libpqxx, but libpq has two output
channels that I know of:

1. The noticer, which should shut up when it's the nonnoticer.  Could
always be a bug there...  Lifetime management problem maybe?

2. Trace output.  Unless you call the connection's trace() function, that
shouldn't happen.  And it spews a lot more than just a few statements.

Jeroen