Question re a "behavioural change" that's happened between 5.3.7.47 and 5.3.9.133. I think it's due to the fix for https://luceeserver.atlassian.net/browse/LDEV-3615 (so ping @bdw429s). Lucee used to preserve the row order of the original queries when UNIONing via QoQ. It no longer does this. Now... it is completely legit to NOT preserve the order, because as far as SQL goes there's no guarantee of ordering unless there's an ORDER BY. But... it is a behaviour change. Should this be noted somewhere?

I would think it's worth nothing in the QoQ docs that a resultsets order is never guaranteed without an explicit ORDER BY clause. You'd think that all devs would know this, but I suspect many do not.

I totally agree that it is the case... But I do think surprise ordering changes could really impact some people's apps, if the behavior has been consistent up to this point.