update schema cache on columns' null-ability or type changes (fix #2101) #2106
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
If a user tries to update column nullability or it's type via
modify tableorSQLsection of the console then update the cache with new column info.[via @anisjonischkeit]
Affected components
Related Issues
fix #2101
Solution and Design
Update
PGColInfoof a column on any ofpgiTypeandpgiIsNullablechange viarun_sql/v1/querymetadata query.Steps to test and verify
Create a table and modify any column's nullability or type. This change should reflect in GraphQL schema.