QoQ doesn't support "column=value" rather than "value as alias"

That’s another “bug” that was fixed in QoQ. Trying to union two queries with different columns is illegal. The old QoQ used to let you get away with it, but we closed the loop hole.

The example from select foo=null was not in use, but I tried using it in some QoQ changes

The given example was a simple change in the script in

<cfscript>
qry= queryNew("name,age,whatever", "varchar,date,int", [
[ "Susi", CreateDate( 1970, 1, 1 ), 5 ],
[ "Urs" , CreateDate( 1995, 1, 1 ), 7 ],
[ "Fred", CreateDate( 1960, 1, 1 ), 9 ],
[ "Jim" , CreateDate( 1988, 1, 1 ), 11 ]
])
query name="q" dbtype="query" {
echo("select name from qry union select age, whatever from qry");
}
writedump(q);
</cfscript>

hmmm, do you have the stack trace from the full example, does it include some hsqldb files?

Thanks for the clarification.

We prefer the syntax select foo = bar, we didn't know it was deprecated, we still use it in SQL server 2017 (and also works in 2019)

I found this inconsistency with SQL while updating some breaking changes since lucee 4.5 update on QoQ’s with a union containing different columns.
select name from qry union select age, whatever from qry

In 4.5 this query was ok and had the columns name, age and whatever
We used this to combine different query results together which have some the same and some extra columns just to be able to sort and loop

I think this was a very useful feature:

select * from rs1
union all
select * from rs2

now needs to be changed to

select <combinedcolumnlist logic with null as missingcolumn> from rs1
union all
select <combinedcolumnlist logic with null as missingcolumn> from rs2