Trond Eivind Glomsrød wrote:
> > Which case-sensitivity issue? The one about table and column names? Or
> > a different one? (sitting confused in Pisgah Forest)
> I remember there were some issues about someone claiming glibc was broken
> (with LANG set to anything but C/POSIX, because it will
Lamar Owen <[EMAIL PROTECTED]> writes:
> Trond Eivind Glomsrød wrote:
> > > Which case-sensitivity issue? The one about table and column names? Or
> > > a different one? (sitting confused in Pisgah Forest)
>
> > I remember there were some issues about someone claiming glibc was broken
> > (wi
Trond Eivind Glomsrød wrote:
> > > it seems like locale support with glibc 2.2.2 is completely broken...
> What exactly is claimed to be broken? If this is the case sensitivity
> issue, that would count as a postgresql bug.
Whatever the sentence above your question means. We'll have to wait on
t
Lamar Owen <[EMAIL PROTECTED]> writes:
> Pimenov Yuri wrote:
> > Greeting!
> > it seems like locale support with glibc 2.2.2 is completely broken...
> > i got huge differences then performing tests in src/test/locale/koi8-r
> > i am running PG7.1 from cvs.
>
> > PS. locale itself isn't broken f
Pimenov Yuri wrote:
> Greeting!
> it seems like locale support with glibc 2.2.2 is completely broken...
> i got huge differences then performing tests in src/test/locale/koi8-r
> i am running PG7.1 from cvs.
> PS. locale itself isn't broken for sure
Locale collation and other issues were substa
Greeting!
it seems like locale support with glibc 2.2.2 is completely broken...
i got huge differences then performing tests in src/test/locale/koi8-r
i am running PG7.1 from cvs.
PS. locale itself isn't broken for sure
---(end of broadcast)---
TI
