| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | "Michael Paesold" <mpaesold(at)gmx(dot)at>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: psql \set case sensitive for boolean (OFF/off) |
| Date: | 2004-09-21 14:24:54 |
| Message-ID: | 667.1095776694@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Am Dienstag, 21. September 2004 13:01 schrieb Michael Paesold:
>> I would recommend to make this check at least case insensitive, because
>>
>> a) Since SQL is case insensitive, the current behaviour is not what you
>> would expect.
> In contrast, psql is case sensitive, so the current behavior is consistent.
True, but recognizing "off" case-insensitively seems like a painless
improvement. What would it be likely to get wrong? (I've forgotten
what the original backwards-compatibility issue alluded to in the
comment was all about, so maybe I'm missing something important.)
If anything I'd think we should migrate towards allowing all the same
alternatives that backend GUC accepts for booleans ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-09-21 16:54:55 | pg_hba.conf additional comment re local line |
| Previous Message | Peter Eisentraut | 2004-09-21 13:51:01 | Re: psql \set case sensitive for boolean (OFF/off) |