From: | Shianmiin Hwang <shianmiin(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: interesting finding on order by behaviour |
Date: | 2011-07-22 18:30:19 |
Message-ID: | 9a83ea96-6192-4257-9b21-721c3701e409@e20g2000prf.googlegroups.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jul 22, 12:20 pm, scott_r(dot)(dot)(dot)(at)elevated-dev(dot)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
>
> Well, if it's case insensitive, then AbC & abc & ABc are all equal, so any order for those 3 would be correct...
>
> --
> Scott Ribe
> scott_r(dot)(dot)(dot)(at)elevated-dev(dot)comhttp://www.elevated-dev.com/
> (303) 722-0567 voice
>
> --
> Sent via pgsql-general mailing list (pgsql-gene(dot)(dot)(dot)(at)postgresql(dot)org)
> To make changes to your subscription:http://www.postgresql.org/mailpref/pgsql-general
Sorry I didn't make it clear, the interesting part is how PostgreSQL
sorts data.
The server encoding is set to UTF8 and collation is united states.1252
The client encoding is Unicode.
From | Date | Subject | |
---|---|---|---|
Next Message | Karl Nack | 2011-07-22 19:15:43 | Implementing "thick"/"fat" databases |
Previous Message | Scott Ribe | 2011-07-22 18:20:09 | Re: interesting finding on order by behaviour |