From: | "Richard Huxton" <dev(at)archonet(dot)com> |
---|---|
To: | "Craig Orsinger" <cjorsinger(at)m5(dot)earthlink_net(dot)invalid>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: NOTIFY/LISTEN Using Embedded SQL (ecpg) |
Date: | 2001-05-23 08:46:27 |
Message-ID: | 003801c0e364$dc3e9ea0$1001a8c0@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
From: "Craig Orsinger" <cjorsinger(at)m5(dot)earthlink_net(dot)invalid>
To: <pgsql-general(at)postgresql(dot)org>
Sent: Tuesday, May 22, 2001 6:08 PM
Subject: [GENERAL] NOTIFY/LISTEN Using Embedded SQL (ecpg)
> [cross posted from comp.databases.postgresql.general]
>
> So, it appears that I can set up my program to LISTEN or
> UNLISTEN using embedded SQL, but I can't get a notification when
> it's sent. Or so I think. _Is_ there a way to get the libpq connection
info
> from the ESQL CONNECT call?
>
> Does anyone have a suggestion (other than completely rewriting
> my application in libpq calls)? Pointers to any examples of how
> this is done would be especially helpful, but any hints would be
> appreciated.
Can you not just wrap up the libpq stuff in it's own module? A "LISTEN X"
doesn't have to be on any particular connection. Don't know whether opening
another connection per program is practical for you.
- Richard Huxton
From | Date | Subject | |
---|---|---|---|
Next Message | rwell | 2001-05-23 08:49:00 | |
Previous Message | Richard Huxton | 2001-05-23 08:39:38 | Re: Re: Select statement |