1
78%
main: 77%

Ran 31 Jul 2026 12:48AM UTC

Files 128

Run time 5s

Badge

Embed ▾

Committed 16 Jul 2026 06:26PM UTC coverage: 77.644%. First build

Job # 30592861347.1

Build Type

push

github

Committed by

web-flow

Commit Message

Support RTE_NAMEDTUPLESTORE in FOR XML/JSON AUTO for trigger transition tables (#4897)

Currently, Babelfish's FOR XML AUTO and FOR JSON AUTO fail with "requires at least one table" when the query source is a named tuplestore specifically the INSERTED and DELETED transition tables inside AFTER triggers. With this change, these transition tables are now recognized as valid sources, and the query produces correct hierarchical XML/JSON output using the tuplestore name (e.g., "inserted", "deleted") as the element/object key name.

The fix was needed because PostgreSQL represents trigger transition tables as RTE_NAMEDTUPLESTORE range table entries, but the FOR AUTO valid-source check only accepted RTE_RELATION, RTE_SUBQUERY, RTE_CTE, RTE_GROUP, and user-defined RTE_FUNCTION.


Task: BABEL-6878
Signed-off-by: Rohit Bhagat <rohitbgt@amazon.com>

Coverage Stats

56028 of 72160 relevant lines covered (77.64%)

584499.6 hits per line

amazon-aurora / babelfish_extensions / 30592861347 / 1
78%
main: 77%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 30592861347.1

amazon-aurora / babelfish_extensions / 30592861347 / 1 78% main: 77%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 30592861347.1

amazon-aurora / babelfish_extensions / 30592861347 / 1
78%
main: 77%

README BADGES
x