Brian Ceccarelli wrote:
> If the words are the same words but letters have different case, then the
> operator is case-sensitive.
> If the words are not the same words, then the operator is case-insensitive
> until the operator reaches the character position in both strings where the
> letters bec
On Tue, Aug 25, 2009 at 8:38 PM, Brian
Ceccarelli wrote:
>
> If the words are the same words but letters have different case, then the
> operator is case-sensitive.
> If the words are not the same words, then the operator is case-insensitive
> until the operator reaches the character position in bo
"Brian Ceccarelli" writes:
> After a long and careful study of this, this is a Postgres bug.
> Postgres is boogering up the sort. The operators < >, and the "order by"
> in the select statement are both case-sensitive and case-insensitive.It
> is inconsistent.
"Consistency" is not a ha
Actually Greg . . .
After a long and careful study of this, this is a Postgres bug.
Postgres is boogering up the sort. The operators < >, and the "order by"
in the select statement are both case-sensitive and case-insensitive.It
is inconsistent. It does not matter what my collating se
On mån, 2009-08-24 at 19:56 -0400, Tom Lane wrote:
> Alvaro Herrera writes:
> > Personally I still think debbugs would suit us perfectly, but 1. I don't
> > have time to handle it, 2. nobody else believes this, 3. the debbugs
> > developers are not very interested in helping us use it.
>
> What i
Alvaro Herrera writes:
> Personally I still think debbugs would suit us perfectly, but 1. I don't
> have time to handle it, 2. nobody else believes this, 3. the debbugs
> developers are not very interested in helping us use it.
What is it that we'd need their help for?
re
On Mon, Aug 24, 2009 at 11:38 PM, Peter Eisentraut wrote:
> On mån, 2009-08-24 at 23:07 +0100, Greg Stark wrote:
>> I think it's a conceit to think we always fix bugs immediately.
>
> I completely agree with that one. The claim that we don't need a bug
> tracker because most bugs get fixed immedia
On mån, 2009-08-24 at 23:07 +0100, Greg Stark wrote:
> I think it's a conceit to think we always fix bugs immediately.
I completely agree with that one. The claim that we don't need a bug
tracker because most bugs get fixed immediately is bogus because a) it's
not true, and b) it doesn't help peo
On Mon, Aug 24, 2009 at 10:16 PM, Peter Eisentraut wrote:
>
> Well, all you'd really need is that if you close a bug, you indicate
> that say via an email header
>
> X-PG-Bugs-Close: 12345
>
> and then spice up the archives display to show that somehow. But the
> chances of getting people to use t
On mån, 2009-08-24 at 20:10 +0100, Greg Stark wrote:
> It's completely email based so we could just treat it as a mailing
> list without having to go visit a web interface to stay up to date. We
> could add CVS/whatever hooks so whenever a commit message says it
> closes a bug it gets closed automa
Robert Haas writes:
> ... It seems to me based on my short
> tenure reading this mailing list that when someone provides a
> reproducible test case of Postgres verifiably DTWT it usually attracts
> plenty of attention and gets dealt with relatively quickly, usually
> with a friendly "thanks for t
On Mon, Aug 24, 2009 at 3:10 PM, Greg Stark wrote:
> On Mon, Aug 24, 2009 at 8:03 PM, Alvaro
> Herrera wrote:
>> Personally I still think debbugs would suit us perfectly, but 1. I don't
>> have time to handle it, 2. nobody else believes this, 3. the debbugs
>> developers are not very interested in
On Mon, Aug 24, 2009 at 8:03 PM, Alvaro
Herrera wrote:
> Personally I still think debbugs would suit us perfectly, but 1. I don't
> have time to handle it, 2. nobody else believes this, 3. the debbugs
> developers are not very interested in helping us use it.
I've been shouting about debbugs forev
Robert Haas escribió:
> On Mon, Aug 24, 2009 at 8:24 AM, Brian
> Ceccarelli wrote:
> > Yes. I understand. It has all to do with Unicode collating sequence. I
> > need to somehow remove this bug from the list, since it is not a bug.
>
> Heh. As far as I understand, there is no list... one th
On Mon, Aug 24, 2009 at 8:24 AM, Brian
Ceccarelli wrote:
> Yes. I understand. It has all to do with Unicode collating sequence. I
> need to somehow remove this bug from the list, since it is not a bug.
Heh. As far as I understand, there is no list... one thing that I
have been worrying abou
, August 24, 2009 4:54 AM
To: Brian Ceccarelli
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #4999: select 'a' < 'A' is true, but should be false
. . .
On tor, 2009-08-20 at 20:24 +, Brian Ceccarelli wrote:
> since the < and > comparison operators seem to
On tor, 2009-08-20 at 20:24 +, Brian Ceccarelli wrote:
> since the < and > comparison operators seem to be case insensitive:
>
> select 'a' < 'Z';-- true
> select 'a' < 'z';-- true
> select 'A' < 'Z';-- true
> select 'A' < 'z';-- true
>
> select 'z' < 'A';-- false
> select
"Brian Ceccarelli" writes:
> since the < and > comparison operators seem to be case insensitive:
They are not, unless you have managed to find a case-insensitive locale
somewhere. In any case we would not think that 'a' = 'A'.
regards, tom lane
--
Sent via pgsql-bugs m
The following bug has been logged online:
Bug reference: 4999
Logged by: Brian Ceccarelli
Email address: cecca...@talussoftware.com
PostgreSQL version: 8.4.0 to 8.2.13
Operating system: Linux and XP
Description:select 'a' < 'A' is true, but should be false . . .
Detai
19 matches
Mail list logo
