Description
Component
This issue pertains to:
CLI -> c/v3-cli
Postgres (for issues that clearly relates to Postgres SQL execution) -> c/v3-ndc-postgres
What is the current behaviour?
- Rename a column in your table in pgsql
- Run
ddn connector introspect sivvy_neon
- Run
model add
,command add
,relationship add
commands.
Observe that renamed column name is still listed as previous column name.
As a result running supergraph build local
or build create
will throw an error similar to this:
ERR Code=opendds-validation Message="invalid metadata: error building schema: invalid metadata: unknown target column name status for field status in object type InsertProvidersObject (in subgraph app)"
What is the expected behaviour?
Expected behavior would be that columns that are renamed are picked up in the introspect command, and updated throughout following commands.
How to reproduce the issue?
- Spinup a hasura ddn -> pgsql connector
- Generate a table, generate some columns
- Run through introspect command
- Rename a column in the table
- Run introspect command again
- Notice issue
Screenshots or Screencast
N/A
Please provide any traces or logs that could help here.
Error log provided above.
Any possible solutions/workarounds you're aware of?
Manually updating the renamed column in the .hml
files in metadata seems to bypass this issue.
Keywords
'rename', 'pgsql rename column'
Activity
edwardoverthere commentedon Mar 4, 2025
Noting that in the connector metadata, the renamed column does show up - however in the app metadata in the
.html
files - column is still named the same.edwardoverthere commentedon Mar 4, 2025
After more inspection, the renamed column DOES show in in app metadata, however the original column still exists. The original column name is whats causing the issues.
seanparkross commentedon Mar 4, 2025
I have notified the team