| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | lockhart(at)fourpalms(dot)org |
| Cc: | Sezai YILMAZ <sezaiy(at)ata(dot)cs(dot)hun(dot)edu(dot)tr>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Turkish locale bug |
| Date: | 2001-02-20 16:47:16 |
| Message-ID: | 12911.982687636@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> Anyway, your proposal is just fine since we haven't decoupled these
> things farther back in the server. But eventually we should hope to have
> SQL_ASCII and other character sets enforced in context.
Now I'm confused. Are you saying that we *should* treat identifier case
under ASCII rules only? That seems like a step backwards to me, but
then I don't use any non-US locale myself...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vadim I. Passynkov | 2001-02-21 00:11:12 | Re: Problem with function aclcontains, features or bug? |
| Previous Message | Thomas Lockhart | 2001-02-20 16:36:19 | Re: Turkish locale bug |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Diehl, Jeffrey | 2001-02-20 16:53:14 | RE: [SQL] handling of database size exceeding physical disk space |
| Previous Message | Thomas Lockhart | 2001-02-20 16:40:22 | Re: beta5 ... |