| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Sezai YILMAZ <sezaiy(at)ata(dot)cs(dot)hun(dot)edu(dot)tr>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | AW: Re: [BUGS] Turkish locale bug |
| Date: | 2001-02-20 17:04:36 |
| Message-ID: | 11C1E6749A55D411A9670001FA687963368207@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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...
I think we need to treat anything that is not quoted as US_ASCII,
iirc this is how Informix behaves. Users wanting locale aware identifiers
would need to double quote those, thus avoiding non ASCII case conversions
alltogether.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-02-20 17:10:11 | Re: Ordering problem with --with-includes |
| Previous Message | Larry Rosenman | 2001-02-20 16:57:14 | Re: Re: beta5 ... |