I can think of quite a few instances (including the one I am going to implement it for) where knowing the order of just a select few ids from the table would be valid and not applying any sort of extra meaning to the ids, speficially in multiuser applications where there could be multiple lists from the same table. Your join table would be at least four columns and all indexed. Clearly more expensive than just getting the three rows you want in the order you want (if it were possible in MySQL).

In 11 years of working with SQL in production environments, I can honestly say I’ve never wanted to do what you are requesting. With that in mind, there is probably a better approach to your problem – in other words, this is not the solution you are looking for.

That being said, it is possible. If you are applying static transformations to dictate order, eg in this case 1=1, 10=2, 5=3 then you can create a translation table, join the id, and then order by the transform id asc. Then hide it with a view, and never, ever tell anyone what you have done.

If you have some sort of strange function for dynamically determining order that is not based on the natural order of any of the columns or combination of columns, you could also write a stored procedure to do it, although philsophically this isn’t much different from having the application do it.

Ich habe einen MySQL Tisch mit einem primären Schlüsselindex auf Identifizierung. Ich würde wie zu, zum Beispiel, wiedergewinnt Punkte mit IDENTIFIZIERUNGEN 1, 7, und 4 in das anordnet.

我在身份证件以一个最初主要的标志有一张 MySQL 桌子。我想要，例如，跟身份证一起取回条款 1，在那种次序中的 7， 4。