The GitHub Actions job "Required - Check" on shardingsphere.git/fix/opengauss-limit-parameter-marker-order has failed. Run started by GitHub user fudianchn (triggered by terrymanu).
Head commit for run: c1fb151bd2a16dbb3c3ab20dffa4495affcb5aa3 / 付典 <[email protected]> Fix openGauss LIMIT offset, row-count parameter marker order For LIMIT offset, row-count (e.g. LIMIT ?, ?), the openGauss visitor visited selectLimitValue (row-count) before selectOffsetValue (offset). Parameter marker indices are assigned in visit order, so this reversed the indices: the lexical first ? (offset) got index 1 and the second ? (row-count) got index 0. Visit the offset before the row-count so the marker indices follow lexical order, matching DorisStatementVisitor. Report URL: https://github.com/apache/shardingsphere/actions/runs/30186553724 With regards, GitHub Actions via GitBox
