fenway

You can't do that... COLUMNS is for a given table only. Use the info_schema tables in MySQL 5 for anything else "fancy".

REPAIR comes in all different flavours... which one are you running? Do you have a recent backup/

Let's see the EXPLAIN output.

I'm sure you *could* figure out a way to "assign" a round-robin list of mysql users.. but again, if your server can't handle the load, it won't help matters much.

Sounds like a few too many fields.

You can always simply update all of the sortorders -- and by that I mean re-create them on every save -- and then there's no incrementing. The 50-style increment is simpy for ease of maintenance, especially if you want to change them by hand.

No kidding... I nearly threw up trying to figure out the equivalent of DATE(myDateTimeField)... all those "magic" numbers and CASTing.... ugh.

Then check the actual dump file... unless some terminator or separator changed, I find this hard to believe.

You basically want a sortorder... easiest way to do this is to guess how many items will be on the list, multiply by 100, then use increments of 50 between successive list items. This allows you to play around with renumbering easily for just one or two, or re-do the whole thing.

Did you CHECK TABLEs?

I've actually used that one, Barand... couldn't believe it had to be so "forced".

Did you do the same for PHP?

If you want that where clause to apply to all of the unioned tables, you need to wrap them in parens.

That subquery can only take a single value back... perhaps you need distinct.

You'd have to break up the user query into part and search for exact matches...

Sounds like you're getting some records twice...?

Well, the question is really if your server can handle more than 50 at a time nayway.

No Windows<=>*NIX conversion?

Yes, but that will change the UID and trigger a DELETE.

This doesn't work? update tbl_cart set cart_qty = cart_qty+1 where cart_id = '67'

MySQL doesn't send mail....

1. I don't actually know what will happen if you try to do "INSERT INTO... SELECT WHERE 0"... but you're missing "SELECT". 2. That won't work. Why not "INSERT... ON DUPLICATE KEY UPDATE"?

What does thsi mean?

How was the data transferred?

What column type is topic_time? UNSIGNED INT? What does FROM_UNIXTIME(topic_time) return? How are you determining that is it blank -- I don't see a column alias, are you running this from phpmyadmin? Also, apparently, FROM_UNIXTIME() takes an optional format parameter as the second argument, so you can do: FROM_UNIXTIME( topic_time, '%m %d %Y' ) Directly.