Skip to content

SGA-11783 Added support for SHOW CHARSET #1974

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

etgarperets
Copy link
Contributor

No description provided.

// MySQL specific statement
// <https://dev.mysql.com/doc/refman/8.4/en/show.html#:~:text=SHOW%20%7BCHARACTER%20SET%20%7C%20CHARSET%7D%20%5Blike_or_where%5D>
ShowCharset {
is_shorthand: bool,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we add a description what this flag does?

Comment on lines +3717 to +3720
ShowCharset {
is_shorthand: bool,
filter: Option<ShowStatementFilter>,
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we switch to using a named struct syntax for this statement? See ref we're trying to move away from the anonymous struct syntax ideally.

We could have something like?

struct ShowCharSet { ... }
Statement::ShowCharSet(ShowCharSet{...})

Comment on lines +3715 to +3716
// MySQL specific statement
// <https://dev.mysql.com/doc/refman/8.4/en/show.html#:~:text=SHOW%20%7BCHARACTER%20SET%20%7C%20CHARSET%7D%20%5Blike_or_where%5D>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// MySQL specific statement
// <https://dev.mysql.com/doc/refman/8.4/en/show.html#:~:text=SHOW%20%7BCHARACTER%20SET%20%7C%20CHARSET%7D%20%5Blike_or_where%5D>
//
[MySQL]: https://dev.mysql.com/doc/refman/8.4/en/show.html#:~:text=SHOW%20%7BCHARACTER%20SET%20%7C%20CHARSET%7D%20%5Blike_or_where%5D

Or something similar, essentially dropping the mention of it being mysql specific, since that can change in the future or other existing dialects might also support it in some form

Comment on lines +3708 to +3714
// SHOW {CHARACTER SET | CHARSET} [like_or_where]
// ```
// where:
// like_or_where: {
// LIKE 'pattern'
// | WHERE expr
// }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// SHOW {CHARACTER SET | CHARSET} [like_or_where]
// ```
// where:
// like_or_where: {
// LIKE 'pattern'
// | WHERE expr
// }
// SHOW {CHARACTER SET | CHARSET}
// ```

Thinking a brief example would be enough. For detailed syntax readers can follow the documentation


#[test]
fn parse_show_charset() {
let _ = mysql().verified_stmt("SHOW CHARACTER SET");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this adds a new node to the AST, can we assert one of the scenarios that the AST looks as expected? For example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants