Skip to content

Correctly set table field from Protocol::ColumnDefinition41 #1535

@altmannmarcelo

Description

@altmannmarcelo

Description

Currently we set the table and org_table from Protocol::ColumnDefinition41 as the reader map node name:

Screenshot 2025-07-18 at 18.13.04.png

Some ORM's rely on this field to populate responses, like a json object:

[
    {
        "q_6b11e2575d821105": {
            "key": "key_something",
            "value": "some_value
        }
    }
]

Upstream sends back the actual table name:

Screenshot 2025-07-18 at 18.13.48.png

[
    {
        "category": {
            "key": "key_something",
            "value": "some_value
        }
    }
]

For generated columns (like count(*) where the field does not strictly trace back to a table, it comes empty:

Screenshot 2025-07-18 at 18.11.49.png

We should investigate if we can send this information down the graph until the reader map.

Change in user-visible behavior

Requires documentation change

Metadata

Metadata

Assignees

No one assigned

    Labels

    High priorityCreated by Linear-GitHub Sync

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions