Just want to confirm that this patch also fixes the error in the application query where I first encountered it. By the way, is it clear why the problem did not manifest with a plain UNION, but did show itself with UNION ALL or no union at all?
Just want to confirm that this patch also fixes the error in the application query where I first encountered it. By the way, is it clear why the problem did not manifest with a plain UNION, but did show itself with UNION ALL or no union at all?