On Wed, Jan 30, 2002 at 10:05:39PM +, peaw peaw wrote:
> Oh I see.
>
> Since I really need this DESC badly, is it sensible to add a 3rd
> column that keeps its values in reverse order(say, SomeBigInt -
> value of col2) ? Then create an index on (col1,col3) and use it
> without the "DESC".
Yes
> Since I really need this DESC badly, is it sensible to
> add a 3rd column that keeps its values in reverse
> order(say, SomeBigInt - value of col2) ? Then create
> an index on (col1,col3) and use it without the "DESC".
Yes. For a signed col2 you can try 0x7FFF - col2. Unsigned I think
you s
Oh I see.
Since I really need this DESC badly, is it sensible to
add a 3rd column that keeps its values in reverse
order(say, SomeBigInt - value of col2) ? Then create
an index on (col1,col3) and use it without the "DESC".
The website does about 10 times more reading than
updating the table. Ther
On Wed, Jan 30, 2002 at 06:21:20PM +, peaw peaw wrote:
> Hello.
> I'm new to this mailing list :+)
>
> I created a mutilple-column index, say
>
> "create index col1_col2 on table_name (col1,col2) "
>
> Both col1 and col2 are mediumint unsigned.
>
> "explain select * from table_name wher
Hello.
I'm new to this mailing list :+)
I created a mutilple-column index, say
"create index col1_col2 on table_name (col1,col2) "
Both col1 and col2 are mediumint unsigned.
"explain select * from table_name where col1='value'
order by col1 DESC,col2 DESC "
shows that the query is still u
