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

issue 376 -- parse and ignore RENAME INDEX statements #378

Merged
merged 1 commit into from
Jul 13, 2016
Merged

Conversation

osheroff
Copy link
Collaborator

#376

@zendesk/rules

@@ -200,7 +200,8 @@ public void testParsingSomeAlters() {
"create table `shard1.foo` ( `id.foo` int ) collate = `utf8_bin`",
"ALTER TABLE .`users` CHANGE COLUMN `password` `password` VARCHAR(60) CHARACTER SET 'utf8' COLLATE 'utf8_bin' NULL DEFAULT NULL COMMENT 'Length 60 for Bcrypt'",
"create table `shard1.foo` ( `id.foo` int ) collate = `utf8_bin`",
"create table if not exists audit_payer_bank_details (event_time TIMESTAMP default CURRENT_TIMESTAMP())"
"create table if not exists audit_payer_bank_details (event_time TIMESTAMP default CURRENT_TIMESTAMP())",
"ALTER TABLE foo RENAME INDEX index_quote_request_follow_on_data_on_model_name TO index_quote_request_follow_on_data_on_model_class_name"
Copy link
Contributor

Choose a reason for hiding this comment

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

oh so this is possible b/c it is just parsing testing, not being executed against mysql 5.5 and 5.6

@dadah89
Copy link
Contributor

dadah89 commented Jul 12, 2016

👍

@osheroff osheroff merged commit 704f8b2 into master Jul 13, 2016
@osheroff osheroff deleted the gh_376 branch December 2, 2020 16:52
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.

None yet

2 participants