Well... that's rather an ambiguous choice of words. Before I created this thread there wasn't a version number for the Debian (ID 8) row, but only a "-". It occurred to me that in the future there might be other releases with the type "2", so I gave it a version number and made another screenshot but I didn't think to revise my post. As it is now, it looks safe to use only the version number to check for the latest of each type.
However, being stuck with this query allowed me to rethink/refine the whole wizard idea. With the regular users in mind, I thought it might be easier for them to present the differences between the Mint releases: regular, long-term and perpetual. I would have to design a 3-tabbed interface that presents in as few words possible what each release type means, which would allow me to present the release details a lot easier to choose. Now making it easier for the user would still require this query I came here to ask for, but then another idea popped up.
Considering I would have to execute that not-so-simple query each time I load the first page of the website, I figured that I might as well use my admin back-end to store the latest IDs in the CMS settings directly - like a cache. After all, they will always be just a few bytes: "123, 132, 138". Then I could simply SELECT * FROM minteditions WHERE release_id IN (123, 132, 138). Right?
The trade-off is I would "bloat" each web page instance with this extra setting but on the other side I could as well use those IDs in other sections of the website whenever I get some brilliant idea. What do you think?
I'm still interested in the query I came here for, as it would give me an extra option for the download wizard, so I'll keep an eye here. Thanks for taking time to answer me.