marco1995
New Contributor II

We were able to reproduce the problem, but it only occurs in Databricks SQL version 2025.10. With version 2024.05, the correct result is obtained.