Your wish is possible to do, but not with SQL.
You're talking about two distinct ideas: querying data and displaying it. If you have no problem querying, all you have to do now is work on the display.
What software is displaying the database? If you're hoping that the MySQL client will manage this for you, I'm afraid you'll be disappointed. You'll have better luck if it's code that you write.
Where do you want the data to end up? In a file? On a display?
UPDATE: If you're using Ajax to query the database, it's the page's job to format it in the manner you like.
You might still find this to be a challenging chore. (It won't look very good, either.)
It's easy to see how this would look for a handful of rows. But what if the query returns tens? Hundreds? How are you limiting the number of rows that come back?
If I want to get this format from the
server, it's because I don't want my
javascript to take too much time to
render the result on the client-side.
Sounds like you're guilty of premature optimization to me.
If you've got that much data coming back from the server I'd say you've got a bigger problem. Make it work on the client where it belongs and then see if your performance is acceptable.
Here's another idea: I believe this way of rendering operator data will look bad and be of little use to operators. What problem are you really trying to solve here? Ajax and libraries like jQuery UI, YUI, etc. offer some really nice ways to render data that go well beyond what HTML can do. Why not investigate some alternative approaches?
If you can use CSS in PHP, I'd recommend using CSS to position your data. Just load the rows into the DOM and let CSS lay it out.