Thanks for the info. That clarify things :)
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/interesting-finding-on-order-by-behaviour-tp4623884p4632301.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pg
Samuel Hwang wrote:
> I ran the same tests in SQL Server 2008R2, Oracle10 and PostgreSQL
> 9.0.4 and found something interesting...
>
> set up
> =
> drop table t1
> create table t1 (f1 varchar(100))
> insert into t1 (f1) values ('AbC')
> insert into t1 (f1) values ('CdE')
> insert into t1 (f1)
On Jul 22, 12:20 pm, scott_r...@elevated-dev.com (Scott Ribe) wrote:
> On Jul 22, 2011, at 11:11 AM, Samuel Hwang wrote:
>
> > results
> > =
> > SQL Server 2008 R2 (with case insensitive data, the ordering follows
> > ASCII order)
>
> > f1
> > ---
> > AbC
> > abc
> > ABc
> > cde
> > CdE
>
> Wel
On Jul 22, 2011, at 11:11 AM, Samuel Hwang wrote:
> results
> =
> SQL Server 2008 R2 (with case insensitive data, the ordering follows
> ASCII order)
>
> f1
> ---
> AbC
> abc
> ABc
> cde
> CdE
Well, if it's case insensitive, then AbC & abc & ABc are all equal, so any
order for those 3 would
On Fri, 2011-07-22 at 10:11 -0700, Samuel Hwang wrote:
> I ran the same tests in SQL Server 2008R2, Oracle10 and PostgreSQL
> 9.0.4 and found something interesting...
> results
> =
> SQL Server 2008 R2 (with case insensitive data, the ordering follows
> ASCII order)
>
> Oracle 10 (data is cas
I ran the same tests in SQL Server 2008R2, Oracle10 and PostgreSQL
9.0.4 and found something interesting...
set up
=
drop table t1
create table t1 (f1 varchar(100))
insert into t1 (f1) values ('AbC')
insert into t1 (f1) values ('CdE')
insert into t1 (f1) values ('abc')
insert into t1 (f1) valu
