fenway

I don't understand teh question.

Then you mysql(i) libraries aren't up to date.

I'm not sure I follow.. you're looking for unique load_ids?

You can always use USE INDEX, or FORCE INDEX if you're stuck.

Maybe I'm missing something here... why not simply timestamp each update? Isn't the most recent the most up to date?

Well, if you're in a transaction, you can set them all to NULL first.

How is it any different?

I'm talking about this.

Please use code tags next time... and don't as for help on skype.

Well, DISTINCT happens after the ORDER BY, so in principle, you can "discard" the others.

And did you check those errors?

You need a LEFT JOIN, not an (implicit) inner join: SELECT list_items.*, categories.* FROM categories LEFT JOIN list_items ON list_items.cat_id=categories.id ORDER BY list_items.cat_id

Try thinking about this from the inside-out, then piece the query back together.

You can use FIELD() in your update statement... just specify the desired order.

A dozen? Maybe i've lost you.

You need to use OLD_PASSWORD().

Huh?

You can use an OR.

Sorry, I don't follow.

You'll have to parse SHOW COLUMNS, or in mysql 5, use the information_schema tables.

Let the DB worry about how to store these -- use datetime if you want a absolute date/time, timestamp if you want it to be timezone-aware. Otherwise, you can display it how ever you'd likeon the way out.

What are you trying to equte to a UID?

Just remember that FULLTEXT is funny.

You'll need another table with the ranges... store min/max, and then link the uid to this table.

Don't do that... use a proper date picker, and have it submit YYYY-MM-DD to the database.