jrgemignani opened a new pull request, #2434:
URL: https://github.com/apache/age/pull/2434
Several VLE regression queries RETURN multiple rows without an ORDER BY, so
their row order depends on traversal/scan order and can vary between runs and
platforms. Add ORDER BY ASC to those queries (on the path, edge-list, or
graphid as appropriate) so the expected output is stable. The queries are
pinned by path (p), edge list (e), or graphid (id(u)/id(v)/id(e[n])) depending
on what each RETURN projects.
Full audit of cypher_vle: all 38 multi-row result blocks were checked. After
this change, every multi-row RETURN is deterministically ordered except the two
SELECT * FROM show_list_use_vle('list01') calls, which are already
deterministic because the function body orders its results with RETURN v ORDER
BY id(v) (added in #2417); their result blocks are unchanged by this commit.
This is a test-only change (regress/sql/cypher_vle.sql and
regress/expected/cypher_vle.out); no extension C code or SQL is modified. Row
counts are unchanged (pure reordering).
All 37 regression tests pass (installcheck) on PostgreSQL 18.3.
Co-authored-by: GitHub Copilot <[email protected]>
modified: regress/expected/cypher_vle.out
modified: regress/sql/cypher_vle.sql
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
