Skip to content

Persist JSON_TABLE PLAN variants as views for round-trip coverage #61

Description

@NikolayS

Three deparse/naming bugs (af6fad8, 160ef27, cd5fd08) hit JSON_TABLE PLAN. Any construct not persisted as a view in the regression DB is round-trip-untested (only pg_upgrade's dump-compare covers this). Add persisted views over JSON_TABLE PLAN variants (nested paths, named/unnamed mixtures, names colliding with generated json_table_path_N, OUTER/UNION/CROSS shapes) with pg_get_viewdef checks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions