fenway

Are you saying your host won't set up remote DB access for you?

Sounds like you want to "number" your records, which is up to your application code to handle.

If you're asking what I think you're asking, your script is going to have to determine which kind of query to compose.

That's up to your application code to "collect".

Or you can simply use an IF() in your ORDER BY clause.

It's not a long list to remember.

I don't follow.

Agreed -- if the LIMIT offset is more than a few percent of the total number of records returned, it's a waste. Also, while I agree that's it's great to program for the future -- and I've been programming and working with databases for about 15 years -- if you look too far into the future, nothing ever gets done.

Or with views.

Don't double-post.

What's wrong with a standard LEFT JOIN?

We're talking about *one* record.

See here.

See here.

Yes, what are you trying to do?

There are literally hundreds of differences between platforms, chipsets, filesystems, memory addressing, etc. that could be responsible. There's just no way to answer your question.

You mean the tables that we haven't seen structures for?

I can't read that jumbled code. and besides, building_lvl.building_id can't be more than one thing at a time, so there is in fact NO SUCH region_id... and there never will be. You're mixing up logical and semantic boolean logic.

I don't follow.

Hierarchical data can be stored in a variety of ways... the stickies talk about this too.

I see nothing wrong with having the application code ignore the first one...

It's incompatible. "Incompatible change: Beginning with MySQL 5.0.42, when a DATE value is compared with a DATETIME value, the DATE value is coerced to the DATETIME type by adding the time portion as 00:00:00. Previously, the time portion of the DATETIME value was ignored, or the comparison could be performed as a string comparison. To mimic the old behavior, use the CAST() function to cause the comparison operands to be treated as previously."

That's up to your script to determine.

If you're not sure how tags relate to blogs, maybe you shouldn't be embarking on building a blog database?

How is this different than, say, a WordPress blog?