From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: (libpq) listen/notify messages are converted to lowercase and/or are case insensitive |
Date: | 2004-08-15 19:05:26 |
Message-ID: | 28828.1092596726@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl> writes:
> Obviously, things work and they probably work as intended, but I wasn't able
> to find anything on this behaviour in the docs. For a moment I thought that
> the syntax rule 'unquoted letters are forced to lowercase' of SQL applied
> here as well, but any double quotes used are simply interpreted as part of
> the name.
You had the right idea: the arguments of listen and notify commands are
identifiers. I don't know what convinced you otherwise.
regression=# listen "Z";
LISTEN
regression=# notify Z;
NOTIFY
regression=# notify "Z";
NOTIFY
Asynchronous notification "Z" received from server process with PID 28818.
regression=# listen z;
LISTEN
regression=# notify "Z";
NOTIFY
Asynchronous notification "Z" received from server process with PID 28818.
regression=# notify Z;
NOTIFY
Asynchronous notification "z" received from server process with PID 28818.
regression=#
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robby Russell | 2004-08-15 19:14:34 | Re: PHP Postgre-MySql call redirector |
Previous Message | Tom Lane | 2004-08-15 18:57:23 | Re: table functions as fields in a select |