Received: from golem.jpl.nasa.gov (IDENT:postfix@dialin-066.jpl.nasa.gov [128.149.231.66]) by hub.org (8.10.1/8.11.0) with ESMTP id e9QDlUU23788 for ; Thu, 26 Oct 2000 09:47:33 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (localhost.localdomain [127.0.0.1]) by golem.jpl.nasa.gov (Postfix) with ESMTP id A5C88E7D2; Thu, 26 Oct 2000 14:03:49 +0000 (UTC) Message-ID: <39F839C5.8A616029@alumni.caltech.edu> Date: Thu, 26 Oct 2000 14:03:49 +0000 From: Thomas Lockhart Organization: Yes X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.15-4mdksmp i686) X-Accept-Language: en MIME-Version: 1.0 To: Cedar Cox Cc: Kovacs Zoltan Sandor , pgsql-interfaces@postgresql.org Subject: Re: signals in ODBC? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200010/221 X-Sequence-Number: 1580 > Huh? First of all, the documentation says that NOTIFY does take an > argument. Secondly, I tried it in two psql's and it appears to work. I > now understand what the other talk was about, LISTEN is only checked once > after each query (correct?). I was not clear on my nonsequiteur: Commercial Ingres allows you to post a *message* with the notifying event, rather than just the event itself. But it is not relevant to the current PostgreSQL implementation, so why did I add to the confusion? I don't know ;) - Thomas