On 26-11-10 13:02, Drake Wilson wrote:
> Quoth luuk34, on 2010-11-26 12:49:53 +0100:
>> The extra column seems to work,
>> but i thought this should work too?
> I would imagine so, at first glance.
>
>> But the ORDER is wrong...
> How? The example you provided seems properly
Quoth luuk34 , on 2010-11-26 12:49:53 +0100:
> The extra column seems to work,
> but i thought this should work too?
I would imagine so, at first glance.
> But the ORDER is wrong...
How? The example you provided seems properly sorted.
> sqlite> SELECT a,b FROM (
> ...>
On 26-11-10 12:37, Drake Wilson wrote:
> Quoth Waldemar Derr, on 2010-11-26 12:24:27 +0100:
>> --Don't working: (Error: 1st ORDER BY term does not match any column in the
>> result set.)
>>
>> SELECT * FROM OrderTest WHERE Price< 200
>> UNION
>> SELECT * FROM OrderTest WHERE
Quoth Waldemar Derr , on 2010-11-26 12:24:27 +0100:
> --Don't working: (Error: 1st ORDER BY term does not match any column in the
> result set.)
>
> SELECT * FROM OrderTest WHERE Price < 200
> UNION
> SELECT * FROM OrderTest WHERE Price > 500
> ORDER BY Price IS 0, Price;
>From
Hello all readers,
following a complete example for reproduce this behaviour (SQLite 3.7.3):
CREATE TABLE IF NOT EXISTS OrderTest (ID AUTOINC, Price FLOAT);
REPLACE INTO OrderTest VALUES (1, 50);
REPLACE INTO OrderTest VALUES (1, 50);
REPLACE INTO OrderTest VALUES (2, 75);
REPLACE INTO
5 matches
Mail list logo