fenway

Well, now I'm really confused -- I only see one LIMIT, and it's a hard-coded constant. Maybe the indentation is messing with my head.

The first problem was that you didn't use CODE tags -- but I've fixed that for you. The second problem is that I don't understand the problem.

Sorry, I don't follow.

No one's going to open a ~800kB word document -- try to summarize you question and post it directly into this thread.

Please echo the actual query.

I'll resist the temptation to argue -- but I agree that the problem is that it's too easy to learn.

The real problem is that PHP is the worst possible language to start with to learn that separation, specifically because it's a glorified template.

Yeah, but never use RIGHT -- you can always re-write it a LEFT join, and that's just the convention.

Let's not even entertain such an idea. The whole purpose of the separation is to force the OP to decide exactly which aspect is causing the problem -- and this also helps people resist the urge to post entire scripts.

No one is going to open your word document -- summarize the relevant portions and post just those properly in this thread.

Which table do you want to delete from?

You mean like a "join"?

Then before you order by distance, you need to "collapse" the city/state pairs -- and decide which distance to user.

Why?

Maybe your timeout is set too high?

Sorry, I don't follow.

select * from `databases` inner join `categories` on `databases`.`id`= `categories`.`id_database`

Well, the last warning is "real" -- and should be addressed -- you have old client libraries.

I don't see a query anywhere.

Sorry, I don't understand the question. You can store text in the database, and lay it out on the page with php however you'd like.

That isn't a valid query -- but the UNION approach should work.

Interesting approach -- but that assumes that there are that number of records before/after.

This topic has been moved to PHP Coding Help. http://www.phpfreaks.com/forums/index.php?topic=288109.0

What do you have now? What do you want to be different?

Basic SQL doesn't provide for this -- but a DB wrapper should easily be able to.