As much as I would think it would be.. Could you think of any reason why
it wouldnt work then for me with the following:-
The version of MySQL is:-
3.23.41 on Linux kernel version 2.4.7-2 on a Redhat 8 server.
The table (table1) has the following fields:-
author varchar(128)
category varchar(64
it's not true, order by is performed before limit. if it was the other
way round , limit would be almost useless
> Hadn't thought about this before, but what it means (I guess) is that LIMIT
> works on the selection, not on the presentation.
>
> What I'm trying to say is that when you consider
You're right, I just forgot to put it in here, as I said the query
works, however, not the way I thought it was supposed to..
>>The query I tried is:-
>>SELECT * from table1 WHERE title LIKE %keyword% ORDER BY title LIMIT 0,10;
>>
>
>The quotes are missing around the string constant.
>
--
Ashwin Kutty writes:
> The query I tried is:-
> SELECT * from table1 WHERE title LIKE %keyword% ORDER BY title LIMIT 0,10;
The quotes are missing around the string constant.
--
Carl Troein - Círdan / Istari-PixelMagic - UIN 16353280
[EMAIL PROTECTED] | http://pixelmagic.dyndns.org/~cirdan/
Hi,
The version of MySQL is (this could be it, I'll try upgrading this now):-
3.23.41 on Linux kernel version 2.4.7-2 on a Redhat 8 server.
The table (table1) has the following fields:-
author varchar(128)
category varchar(64)
title varchar(128)
location varchar(64)
platform varchar(40)
note va
Hi,
> Order By clause without Limit returns:-
> A
> B
> C
> C
> C
> C
> C
> C
> M
> N
> T
> W
>
> Order By clause with Limit returns:-
>
> C
> C
> C
> C
> C
> C
> M
> N
> T
> W
>
> Is there any way to fix this, so that the results with the limit comes
> out starting with the A and then moves on t
