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

Add support for MySQL's mandatory ON clause in the DROP INDEX statement #4179

Closed
lukaseder opened this issue Apr 8, 2015 · 2 comments
Closed

Comments

@lukaseder
Copy link
Member

MySQL's DROP INDEX statement has a mandatory ON clause, as index names are not unique:
https://dev.mysql.com/doc/refman/5.7/en/drop-index.html

@frodnix
Copy link

frodnix commented May 22, 2017

Now jooq have the following problem - I can't code database-independent DROP INDEX. I suppose the correct way should be dropIndex(indexName).on(tableName) and jooq should produce ON clause for MySQL and no ON clause for other databases.

@lukaseder
Copy link
Member Author

You're right, thank you very much for the hint. Indeed, we'll do that for jOOQ 3.10. I've created a separate feature request: #6258

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

No branches or pull requests

2 participants