fenway

In general, you would try to put your field value outside the "between", so that an index could be used...

That's not echoing the query to the screen... that's copying and pasting php code, which I've already seen. It doesn't help me. Store that query in a variable, and echo that variable to the screen, then post it here -- just the sql, not the php.

There's nothing "wrong" with these characters, and you may or may not want to permit them for your own reasons. But it has nothing to do with mysql, as long as you espape them, they are treated just like normal characters. You can't tell someone whose last name is O'Brien to change their last name.

What have you tried so far?

Sounds like the job for insert on duplicate update.

We don't need all of that code... echo the insert query to the screen.

How?

Yes, fake the other columns: SELECT profileID, details1, details2, details3 FORM linkRel where profileID='0' UNION SELECT profileID, details1, details2, NULL AS details3 FROM metaTag where profileID='0' UNION SELECT profileID, details1, NULL AS details2, NULL AS details3 FROM pageTitle where profileID='0' ?

Do you have a working select statement?

No need for PM... just make sure you escape special characters with mysql_escape_string().

Yes, I understand, have you been able to connect without ssh?

That's right, don't escape your alias!

Where you put the column usually has little to do with optimization, but rather normalization.

For UIDs, use INT UNSIGNED. For everything else, choose unsigned intelligently. Forget about speed, it makes no difference.

From where? to where/

You mean like a sortorder?

SSH?

Not sure what you mean... you already have the data from the db...

Depends on how big they are, how much/often you're serving, etc...

You can "convert" a multi-table select into a multi-table update...

Yikes... can't you collate it "down" without have to do all those replaces..? Still we have to narrow down the column that's the problem, and I don't see collation info.

I'm very confused... do you need all of this data back all of the time?

Too few records also causes problems.

Full-text queries behave like that sometimes, especially if there are too many results.

Sometimes magic_quotes can be enaged.