On 8/2/06, Flemming Frandsen <ff@xxxxxxxxxxxxxxx> wrote:
Ian Harding wrote: > NOTIFY interacts with SQL transactions in some important ways. > Firstly, if a NOTIFY is executed inside a transaction, the notify > events are not delivered until and unless the transaction is > committed. This is appropriate, since if the transaction is aborted, > all the commands within it have had no effect, including NOTIFY. But > it can be disconcerting if one is expecting the notification events to > be delivered immediately. Yes, that's very nice, but it doesn't have *anything* to do with what I posted about.
Quite true, but it does indicate, to me at least, the fact that this is a SQL command and doesn't take effect until committed.
