ydb/yql/essentials/tests/sql/sql2yql, branch main

YQL-20631: Support WITH CTE columns and fix UNION column order for YqlSelect

2026-06-23T08:17:53Z

Implemented a column names specification for a WITH CTE. It requires a column order derivation. It was not working on `YqlSelect` until PR https://nda.ya.ru/t/qOC3TNqn7gAcy6 was merged. Also there was a bug with `UNION` column order inference, which is essential for RECURSIVE queries. There was compatibility problems with `PgSelect` `UNION` positional column order semantics, so it was tweaked in `YqlSelect` mode. commit_hash:c96192270ca6d51eaa0cb39cf59b65c3951ce3fe

YQL-21048: Fix GROUPING SETS aggregation optionality on YqlSelect

2026-06-22T12:21:21Z

This patch fixes the query . If you remove `PRAGMA YqlSelect`, you'll see that it works on a legacy translation. It is also required to fix PR , because saving a column order makes the bug visible. The `nokey` flag of `YqlAgg` callable was renamed to `as_optional` and also an expansion was fixed by rewriting `MatchType` on `Optional` to `AsOptionalType` to handle `Null` and `pg` types properly. commit_hash:dc435437e87006c79bb93984d65931aaf5901af4

YQL-21338: Better error message

2026-06-22T09:58:40Z

#### Better error messages for window frame expressions ✎ - Improved error messaging for RANGE window frames to provide more specific information about unsupported column types and invalid ORDER BY expressions - Removed obsolete error handling for multiple sort columns and simplified the sort traits variant - Enhanced error reporting with detailed type information when RANGE frames are used with non-numeric or complex expressions - Added better handling for error types in ORDER BY expressions with improved diagnostic messages including nested error details - Updated error messages to be more descriptive and actionable, showing the actual column type causing the issue - Added new test cases covering various error scenarios including NULL types, optional types, and invalid expressions Autodescription by Yandex Code Assistant commit_hash:1d2301ac75b3ff7bc9ca97213e9005507654e56b

YQL-20631: Support RECURSIVE WITH CTE on YqlSelect

2026-06-19T13:23:50Z

Implemented a RECURSIVE WITH CTE translation for YqlSelect. It relies on YqlSelf callable. As this callable binds to enclosing YqlSelect, the diagnostic that subquery can't reference an enclosing RECURSIVE WITH CTE was added, it is better, that an existing for pgSQL, where just "table not found" is emitted. The core idea under RECURSIVE handling is that a "not ready" CTE entry is added to a namespace (with a `nullptr` node), so it can be recognized. Checked some interesting test cases and wrote TODOs. commit_hash:65b8646e0615ae070b04822ce7af24245c203bbe

YQL-20631: Support simple CTEs on YqlSelect

2026-06-18T15:30:10Z

The first iteration on WITH CTE support. Only simple CTEs are supported. Properties: 1. Redefinition is forbidden. 2. Shadowing is supported. 3. Nested WITH CTEs are supported. Following features are not yet implemented: 1. Column names specification. There is an assertion failure at core because of an absent column order when translating it like for the `PgSelect`. 2. `RECURSIVE` is postponed. There a more sophisticated translation with `YqlSelf` callable is required. Also there was a potential defect because of an empty `Id` result not expected. commit_hash:759676d8a9d369f7eedd9b87f79455b2f8a9fcff

YQL-21321 don't check for persistable in agg traits typecheck

2026-06-17T14:11:06Z

#### `YQL-21321`: Adjust type checking for aggregate traits ✎ - Replaced persistable type check with computable type check during aggregate trait validation to allow more flexible type handling - Added new test cases to verify the behavior of unused aggregate types and ensure proper error reporting - Updated canonical data and test artifacts to reflect the changes in type checking logic and error messages Autodescription by Yandex Code Assistant commit_hash:e14b06e4a135d9aef8ae78a75c3fb23d983365a6

Use Cons! in translator instead of Nth

2026-06-17T10:32:02Z

commit_hash:ec28efb62da755bd372bba274c8eaa0f3f5233f3

YQL-21321 deep error check for EnsurePersistable

2026-06-16T18:49:43Z

#### Deep error checking for EnsurePersistable ✎ - Replaced shallow error checking with comprehensive error detection in `EnsurePersistable` functions to ensure all type annotation errors are properly identified - Introduced new `HasAnyError` function that performs thorough error traversal to catch nested or indirect type errors - Updated test cases to verify error handling behavior and ensure proper error reporting for incompatible types in SQL operations - Enhanced type annotation validation to provide more reliable persistence checks for expression nodes Autodescription by Yandex Code Assistant commit_hash:019e5924e7d6bdfea7fa46be3da3615b17727b76

Fix PayloadRenameOverWindow in overwrite case

2026-06-11T11:41:03Z

commit_hash:867eb4209058a877aa60f86931daddf1e25ac600

YQL-21297: Handle Interval64 in aggregate/window

2026-06-10T17:56:59Z

commit_hash:10c8d54083c7064e63989ad9c341711fe84409b4