| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Nicolai Tufar" <ntufar(at)apb(dot)com(dot)tr> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Locale-dependent case conversion in {identifier} |
| Date: | 2002-11-30 04:24:08 |
| Message-ID: | 25510.1038630248@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-general pgsql-hackers |
"Nicolai Tufar" <ntufar(at)apb(dot)com(dot)tr> writes:
> So I have changed lower-case conversion code in scan.l to make it purely
> ASCII-based.
> as in keywords.c. Mini-patch is given below.
Rather than offering a patch, you need to convince us why our reading of
the SQL standard is wrong. ("Oracle does it that way" is not an
argument that will carry a lot of weight.)
SQL99 states that identifier case conversions are done on the basis of
the Unicode upper/lower case equivalences, so it seems clear that they
intend more than ASCII-only conversion for identifiers. Locale-based
conversion might not be an exact implementation of the spec, but it's
surely closer than ASCII-only.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2002-11-30 05:55:07 | Re: 7.4 Wishlist |
| Previous Message | greg | 2002-11-30 03:33:58 | Fwd: eWeek Article |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2002-11-30 05:55:07 | Re: 7.4 Wishlist |
| Previous Message | Alvaro Herrera | 2002-11-30 03:37:00 | Re: ALTER TABLE & COLUMN |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-11-30 04:32:23 | Re: Planning for improved versions of IN/NOT IN |
| Previous Message | Vince Vielhaber | 2002-11-30 04:00:10 | Re: Postgres 7.3 announcement on postgresql.org |