[Bug report] PostgreSQL query table information incorrect #1171
Assignees
Milestone
Comments
jerryshao
pushed a commit
that referenced
this issue
Dec 18, 2023
…loaded under multiple schemas. (#1183) ### What changes were proposed in this pull request? Fix a bug where the same table name can be loaded under multiple schemas ### Why are the changes needed? Fix: #1171 ### Does this PR introduce _any_ user-facing change? NO ### How was this patch tested? UT Co-authored-by: Clearvive <[email protected]>
github-actions bot
pushed a commit
that referenced
this issue
Dec 18, 2023
…loaded under multiple schemas. (#1183) ### What changes were proposed in this pull request? Fix a bug where the same table name can be loaded under multiple schemas ### Why are the changes needed? Fix: #1171 ### Does this PR introduce _any_ user-facing change? NO ### How was this patch tested? UT Co-authored-by: Clearvive <[email protected]>
jerryshao
pushed a commit
that referenced
this issue
Dec 19, 2023
…loaded under multiple schemas. (#1195) ### What changes were proposed in this pull request? Fix a bug where the same table name can be loaded under multiple schemas ### Why are the changes needed? Fix: #1171 ### Does this PR introduce _any_ user-facing change? NO ### How was this patch tested? UT Co-authored-by: Clearvive <[email protected]> Co-authored-by: Clearvive <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe what's wrong
PostgreSQL should display the specified database and schema when loading table fields, otherwise it will be loaded into tables that do not belong to that database. schema
Error message and/or stacktrace
How to reproduce
Creating the same table under different schemas
Additional context
No response
The text was updated successfully, but these errors were encountered: