At 14:01 25/10/00 -0400, Tom Lane wrote:
>> LISTEN happens on a table (or actually any arbitrary name; it doesn't
>> need an underlying object). But afaik you have to do a query to get your
>> LISTEN to fire on the client, since none of our clients are
>> multithreaded.
>
>I don't know whether the ODBC driver, or even the ODBC API, allows for
>asynchronous NOTIFY, but it works just fine in plain libpq. My former
>company used to rely on NOTIFY all the time for cross-client signaling.
>It hasn't been necessary to issue dummy queries since 6.4 or so.
>
ODBC 1 & 2 don't. I doubt 3 does either. What would be really kind of nice
is if we had:
LISTEN <name> [<port>]
which would send notifications to the specified port on the client machine.
Then with a small amount of effort, ODBC users could take advantage of
notifications. Does this sound easy/hard and worthwhile?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \| | --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/