| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | "Scot Loach" <sloach(at)sandvine(dot)com>, pgsql-odbc(at)postgresql(dot)org, "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com> |
| Subject: | Re: notice handler in libpq-based driver |
| Date: | 2005-09-07 14:48:59 |
| Message-ID: | 27209.1126104539@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> No, I'm not sure how to handle this either - the old driver handled it
> in the socket code along with other messages. I'm not sure how, with the
> noticeProcessor, we would associate notices with specific statements or
> connections.
IIRC, the notice processor is passed a void pointer that you specify
when you set up the notice hook. Typically you'd give it a pointer to
your own data structure describing the connection. It should be able to
find out whatever it needs to know from there.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2005-09-07 15:09:10 | Re: notice handler in libpq-based driver |
| Previous Message | Dave Page | 2005-09-07 13:02:42 | Re: changed behavior in libpq odbc driver |