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/04/28 15:00:24 UTC

[GH] (shardingsphere/fix/opengauss-limit-offset-param-order-34961): Workflow run "Required - Check" failed!

The GitHub Actions job "Required - Check" on shardingsphere.git/fix/opengauss-limit-offset-param-order-34961 has failed.
Run started by GitHub user daguimu (triggered by linghengqian).

Head commit for run:
d51cd6125af64f84b70b730119ee2340efedb49f / daguimu <da...@gmail.com>
Fix openGauss LIMIT offset, row-count parameter marker order

openGauss supports MySQL-style `LIMIT offset, count` shortcut. The
visitor was building the LimitSegment by visiting the row-count child
before the offset child, so parameter marker indices were assigned in
reverse lexical order.

With `LIMIT ?, ?`, the first `?` would be bound to row-count and the
second `?` to offset, making user parameters arrive swapped at runtime.

Visit offset first, then row-count, to match lexical order.

Fixes #34961

Report URL: https://github.com/apache/shardingsphere/actions/runs/24869346186

With regards,
GitHub Actions via GitBox