Skip to content
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

PS-8963 fix 8.4: SEQUENCE_TABLE Issue #5332

Conversation

percona-ysorokin
Copy link
Collaborator

No description provided.

https://perconadev.atlassian.net/browse/PS-8963

Introduced new 'PERCONA_SEQUENCE_TABLE' reserved keyword which is supposed
to be a safe replacement for 'SEQUENCE_TABLE' which is now considered to
be deprecated.
Currently both have identical behavior except the fact that the latter now generates
a deprecation warning.

As an intermediate step before deprecated 'SEQUENCE_TABLE' is removed the
MySQL parser has been modified so that 'SEQUENCE_TABLE' is no longer a
reserved keyword and can now be used as a regular MySQL identifier (table name,
column name, alias name, etc).

'SEQUENCE_TABLE' token added to the list of the non-reserved keywords
('<ident_keywords_unambiguous>') in the Percona Server grammar file
('sql_yacc.yy').

Added new 'main.percona_sequence_table_keyword' MTR test case that check
various scenarios of 'SEQUENCE_TABLE' used as a simple table name, as an alias,
or a table function.

Re-recorded 'main.information_schema_keywords' MTR test case because
'SEQUENCE_TABLE' is no longer a reserved keyword.

Updated a number of existing MTR test cases with new 'PERCONA_SEQUENCE_TABLE()'
table-level function instead of 'SEQUENCE_TABLE()'.
Copy link
Contributor

@dlenev dlenev left a comment

Choose a reason for hiding this comment

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

Hello Yura! The patch LGTM.

@percona-ysorokin percona-ysorokin merged commit 7886958 into percona:release-8.4.0-1 Jun 25, 2024
23 of 24 checks passed
@percona-ysorokin
Copy link
Collaborator Author

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.

3 participants