Skip site navigation (1) Skip section navigation (2)

PQsetNoticeReceiver issues

From: Jonathan Gardner <jgardner(at)jonathangardner(dot)net>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: PQsetNoticeReceiver issues
Date: 2004-01-18 08:27:29
Message-ID: 200401180027.35723.jgardner@jonathangardner.net (view raw or flat)
Thread:
Lists: pgsql-interfaces
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm writing a onion-skin thick wrapper around the libpq library in Python. 
This is my way of getting back into C and also getting a lot more 
familiar with PostgreSQL.

I've run into a conundrum with the PQsetNoticeReceiver function call. How 
do you set it back to the original default? How do you call the 
appropriate PQnoticeProcessor as well?

I expected to find a function in the library like PQdefaultNoticeReceiver, 
but either I'm looking at the wrong file or it doesn't exist. I also 
expected to see PQdefaultNoticeProcessor, but nothing turned up. While 
the documentation contains a neat implementation of a default 
PQnoticeProcessor, it doesn't seem to be defined in the library.

Another issue that I am running into is that while the documentation 
claims that PQnoticeReceivers may call PQnoticeProcessors, it doesn't 
mention how this is to be done. How do I find out which PQnoticeProcessor 
is connected to a PGresult?

I though that I could perhaps access it directly by including libpq-int.h, 
but that seems to be missing from 7.4 now. (Should the note about not 
using libpq-int.h in the documentation be removed now that it isn't there 
anymore?)

- -- 
Jonathan Gardner
jgardner(at)jonathangardner(dot)net
Live Free, Use Linux!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFACkN1WgwF3QvpWNwRAnzxAKCHDTprHc0d7aC6gRzUleU6zgy59wCfe8/v
0E9jN6p+s8cceiBDUbc9wGE=
=gvi9
-----END PGP SIGNATURE-----

Responses

pgsql-interfaces by date

Next:From: Peter EisentrautDate: 2004-01-18 10:19:58
Subject: Re: PQsetNoticeReceiver issues
Previous:From: Goulet, DickDate: 2004-01-16 20:01:20
Subject: ECPG on WinDoze

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group