fix: use schema instead of database for GaussDB M mode view DDL - #6166
Open
AndrewDi wants to merge 1 commit into
Open
fix: use schema instead of database for GaussDB M mode view DDL#6166AndrewDi wants to merge 1 commit into
AndrewDi wants to merge 1 commit into
Conversation
In GaussDB M mode (MySQL-compatible), the schema parameter received from the frontend is the actual schema name (e.g. dbe_perf), not the database name (e.g. pubdb). The previous code passed the database name to mysql_object_source_sql, generating SHOW CREATE VIEW `pubdb`.`view_name` which failed because pubdb is a database, not a schema. Fix gaussdb_m_view_object_source_sql to use the schema parameter instead of the database parameter when building the SHOW CREATE VIEW SQL.
Contributor
Author
|
@zipg 修复获取view的schema错误 |
github-actions
Bot
added
area/core
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In GaussDB M mode (MySQL-compatible), the schema parameter received from the frontend is the actual schema name (e.g. dbe_perf), not the database name (e.g. pubdb). The previous code passed the database name to mysql_object_source_sql, generating SHOW CREATE VIEW
pubdb.view_namewhich failed because pubdb is a database, not a schema.Fix gaussdb_m_view_object_source_sql to use the schema parameter instead of the database parameter when building the SHOW CREATE VIEW SQL.