fenway

You can order by MATCH..AGAINST... too -- otherwise, you'll need to roll-your-own weighting algorithm.

You can use binary... those are numbers, too.

ON... goes before TO...

This is ultimately a pagination issue... you can't use IDs for this.

Because not every query can utilize every index (very true for 4.1) and it's expensive to keep it up to date.

Did you try (UNTESTED): UPDATE tb_users tb WHERE EXISTS(SELECT tb2.ip FROM tb_users tb2 WHERE tb.ip=tb2.ip AND tb.username<>tb2.username) SET tb.suspen='logged'

What do you mean you don't have indexes? WHY NOT?????

I only see one query....

You can definitely load data in bulk from CSV... in fact, newer versions of MySQL can even using the CSV file as a storage engine. If you're having trouble, you likely haven't exported your XLS file correctly, or your LOAD DATA INFILE statement is wrong. Post the relevant info.

A LEFT JOIN is also an option here...

I'm very confused... you want to run the update for only the matching users from the select? Your current update has no where clause!`

Impossible to say... what makes you think it's wrong?

It's not weird -- you've corrupted the ON clause. What you want for the second query is this: SELECT components.manufacturer, components.part_num, components.stock FROM components LEFT JOIN $bod ON (components.part_num=$bod.manufacturer_num) WHERE $bod.manufacturer_num IS NULL

Oh sure, Barand gets the credit ;-) lol.... j/k...glad you got it working.

If by "line" you mean "field", then likely yes.

Sounds like you're missing a call to mysql_select_db.... impossible to tell since we haven't seen any code.

According to the refman page, it is a write permission issue, and has nothing to do with innodb.... But your second problem does... what version? Sounds like you have --skip-innodb... what does SHOW ENGINES say?

The code snippet is very confusing... 1) you named variables "query" that are really "results" 2) query3 is the same as query7, but you use query2, which is never defined... 3) query7 is the same as query1 No wonder you're getting strange things... GIGO.

That's generally the way that I do it, too.

"between" makes no sense... mysql doesn't have loops... and your use $db twice, so the queries are identical.

Write permissions?

See here.

MyISAM locks don't come from that many places...

you can & it with a bitmask.

It's quite easy if you check DAYOFWEEK() [1..7, starts of Sunday].