From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | Chris Travers <chris(at)travelamericas(dot)com>, Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, "Aly S(dot)P Dharshi" <aly(dot)dharshi(at)telus(dot)net>, "Gavin M(dot) Roy" <gmr(at)ehpg(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL Gotchas |
Date: | 2005-10-14 14:39:54 |
Message-ID: | 9698.1129300794@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> and the lexer thinks that it should fold unquoted identifiers to upper
>> case, then the catalog entries defining these names had better read
>> PG_CLASS, RELPAGES, and MAX, not the lower-case names they contain
>> today.
> Well the case of unquoted identifiers could be finessed by having it match
> RELPAGES first and fail over to relpages second. It could even be made to
> match RelPages and whatever if there isn't any ambiguity.
[ shrug... ] Sure, you could invent some rule that might sort of work
most of the time. But then you've abandoned the sole rationale for the
entire project, which is to *adhere to the standard*. Any kind of funny
business with the case folding rules will make things worse not better
from that standpoint.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2005-10-14 14:54:19 | Re: On "multi-master" |
Previous Message | Jan Wieck | 2005-10-14 14:34:53 | Re: PostgreSQL Gotchas |