fenway

Um, no. You're likely not connecting to the right host/DB.

Not really... I'm not suggesting you hard-code the number... I was confused by your suggestion to combine min and count. min of a single number is that number. Unless you mean the min of *all* places, not each palce.

You don't reach 13K posts by accident.

Then REPLACE() the characters you don't want, and then order by that.

Wait a sec... if he eats 4 times at a location, then it's 4... the MIN() won't make it less. I'm confused.

Neither do any of us... turn on error reporting, and as gizmola said, let's make sure we're talking about the same code here.

Well, you could use a HAVING clause to make tally = whatever you want.

That seems impossible... wait, it's it mysql_num_rows()?

You can read more about this here...

Perhaps you should read through this first.

You have list =, not list .= -- you're replacing it, and only getting the last row's value.

During "each" year? Then you need to group by year and pick the "last" week (with MAX(), I presume).

It specifies "display width"... it's just silly. Data type specifies maximum size. And if you're referring to an auto-increment field, you probably want UNSIGNED, too.

Do you know which ones you want to skip?

That's a limitation on update a table from "itself".

That's a bit vague...

I know how to read code. And yes... that's precisely why it's not working -- don't renumber until you SAVE, the gaps don't matter. I'm moving this to the php foru

Nothing limits the number of rows. Don't specify that (4).

order is a reseved keyword... pick another name for the field, like sortorder.

You talk about "gaps"... you can't have gaps until you have numbers, which means you're assigning them too soon.

This really isn't a mysql issue... it's about how to manipulate sort orders; the fact that you're storing it a DB is another issue entirely (i.e. there's no logic on the mysql side, it's just an update). Easiest way is to ignore existing numbers, and update ALL of them agian.

Had you read this?

Yup, 4.1 doesn't care.

Not a bad approximation.

There is an ALL subquery option...