diff options
| author | vitya-smirnov <[email protected]> | 2026-06-19 15:39:51 +0300 |
|---|---|---|
| committer | vitya-smirnov <[email protected]> | 2026-06-19 16:23:50 +0300 |
| commit | 3d79ff71a5cb0a74ef11f187827a2955ff83b355 (patch) | |
| tree | eb97625304d42cedbd31f011f0894ebba13df353 /contrib/python/ipython/py3/IPython/utils/traitlets.py | |
| parent | 89c0e29c8f9ba29ecdc736fefda87286482ac213 (diff) | |
YQL-20631: Support RECURSIVE WITH CTE on YqlSelect
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
Diffstat (limited to 'contrib/python/ipython/py3/IPython/utils/traitlets.py')
0 files changed, 0 insertions, 0 deletions
