| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | lockhart(at)fourpalms(dot)org, 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-23 17:53:23 |
| Message-ID: | 3A96A393.76D41A37@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
> > 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...
(Just a follow up...)
I haven't had time to review the spec on this, but my recollection is
that the entire SQL language can be described using the SQL_ASCII
character set. I would assume that this might include unquoted
identifiers. I'd looked at much of this some time ago, but not recently
so my memory might be faultly (for, um, not the first time :/
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-02-23 17:58:50 | Re: Turkish locale bug |
| Previous Message | Thomas Lockhart | 2001-02-23 17:48:45 | Re: Date calculation produces wrong output with 7.02 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-02-23 17:58:50 | Re: Turkish locale bug |
| Previous Message | Tom Lane | 2001-02-23 17:51:00 | CURRENT_DATE and CURRENT_TIME are broken |