Gerald L. Clark wrote:
James Tu wrote:
I was a little to quick with the send button.
Can you do a query like this:
(I know that the * syntax is not correct, but is there something
equivalent to it?
SELECT from cars
WHERE
make=5 AND
model=* AND
body_color=7 AND
tire_type = *
James Tu wrote:
I was a little to quick with the send button.
Can you do a query like this:
(I know that the * syntax is not correct, but is there something
equivalent to it?
SELECT from cars
WHERE
make=5 AND
model=* AND
body_color=7 AND
tire_type = * AND
hub_caps_type =
I was a little to quick with the send button.
Can you do a query like this:
(I know that the * syntax is not correct, but is there something
equivalent to it?
SELECT from cars
WHERE
make=5 AND
model=* AND
body_color=7 AND
tire_type = * AND
hub_caps_typ
Hi James, all,
James Tu wrote:
What do you guys think of this approach...
Always query on all 5 columns...and then create a multicolumn index
using all 5 columns?
From a database point of view, that would be best -
but I am not sure whether it fits your application and the users.
Some poi
What do you guys think of this approach...
Always query on all 5 columns...and then create a multicolumn index
using all 5 columns?
-James
On Apr 24, 2007, at 11:42 AM, James Tu wrote:
Thanks Mike.
So let's say I have in index on each of the columns below...and I
do a search for
make
Thanks Mike.
So let's say I have in index on each of the columns below...and I do
a search for
make=5
model=2
body_color=7
tire_type=11
hub_caps_type=1
MySQL will only pick one of them right? Let's say it picks make_index.
Then what does it do? Does it scan the entire set of results
retur
James,
A lot depends on how many rows you are searching on. If you only
have a couple thousand rows, then a table scan will still be fast. If you
are searching more rows, say more than 10,000, then using the proper index
will speed things up. Using a compound index is only useful if t
