You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2026/02/25 02:51:31 UTC
[GH] (shardingsphere/fix/37770-unary-not-scalar-subquery): Workflow run "Required - Check" failed!
The GitHub Actions job "Required - Check" on shardingsphere.git/fix/37770-unary-not-scalar-subquery has failed.
Run started by GitHub user ym0506 (triggered by linghengqian).
Head commit for run:
41a4650c4c92b232b2edcd2599096132cb809ae3 / ym0506 <at...@naver.com>
[Parser][PostgreSQL] Handle unary NOT as NotExpression in AExpr
Fixes #37770.
PostgreSQL visitor could parse unary NOT expression in scalar-subquery form as CommonExpressionSegment, which prevents recursive table extraction for inner subquery tables.
This can skip sharding table rewrite and send logical names (for example t23/t22) to backend.
Add explicit unary NOT handling in visitAExpr and a regression test for the reported SQL shape.
Report URL: https://github.com/apache/shardingsphere/actions/runs/22378906831
With regards,
GitHub Actions via GitBox