Message-ID: <4EAC6D46.1060602@greenpeace.org>
Date: Sun, 30 Oct 2011 10:16:54 +1300
From: Jan Bakuwel <jan.bakuwel@greenpeace.org>
Organization: Greenpeace (http://www.greenpeace.org)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.2.23) Gecko/20110921 Lightning/1.0b2 Thunderbird/3.1.15
MIME-Version: 1.0
To: Phil Couling <couling@gmail.com>
CC: Pavel Stehule <pavel.stehule@gmail.com>, pgsql-sql@postgresql.org
Subject: Re: Different order by behaviour depending on where clause?
References: <4EAA3550.7080609@greenpeace.org>
	<CAFj8pRBRJkJS-KSOL-1wdnhmG4ZEv9LFfXmUZFxmzUfzA+ymgw@mail.gmail.com>
	<CANWftz+4LefBCLigcyFY5L+0B6wTcKL9FzHC2QuaJvx7KZhT3g@mail.gmail.com>
In-Reply-To: 
 <CANWftz+4LefBCLigcyFY5L+0B6wTcKL9FzHC2QuaJvx7KZhT3g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi Phil,

Thanks for your reply.


On 28/10/11 23:25, Phil Couling wrote:
> Hi Jan
>
> It is my understanding that a select query without "order by" has an
> undefined order.
> Though I'm sure you understand the dangers of using something which is
> undefined, I'm going reiterate them here:

I think you might have misread my email, I'm quoting:

"I have a compound query with some grouping, having and order by's saved
as a view, say with name "myview".

So... I am using explicit order by's. The problem (now solved) was that
I somewhere subtle "hidden" in one of my subqueries, type casted a row
(varchar to int) but omitted to do the same one or two "levels up". This
messed up my sorting. Once I applied the type cast in every single bit
of statement or all (sub)selects, all was OK.

kind regards,
Jan