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

Jump to bottom

Fix @Support on ALTER TABLE .. RENAME INDEX #11614

Closed
3 tasks done
lukaseder opened this issue Mar 11, 2021 · 1 comment
Closed
3 tasks done

Fix @Support on ALTER TABLE .. RENAME INDEX #11614

lukaseder opened this issue Mar 11, 2021 · 1 comment
Labels
C: Documentation E: All Editions P: Medium R: Fixed T: Defect
Projects
3.13 DDL interpretation
Milestone
Version 3.15.0

Comments

@lukaseder
Copy link
Member

lukaseder commented Mar 11, 2021 •
edited

The ALTER TABLE .. RENAME INDEX and ALTER INDEX .. RENAME TO syntaxes are equivalent, but they don't have the same @Support content.

We should have some integration tests validating the equivalence of such synonyms. Complete list of lacking support:

  • HANA
  • MariaDB
  • MemSQL
@lukaseder lukaseder added this to the Version 3.15.0 milestone Mar 11, 2021
@lukaseder lukaseder added this to To do in 3.13 DDL interpretation via automation Mar 11, 2021
@lukaseder lukaseder changed the title Missing MARIADB @Support on ALTER TABLE .. RENAME INDEX Fix @Support on ALTER TABLE .. RENAME INDEX Mar 11, 2021
lukaseder added a commit that referenced this issue Mar 11, 2021
@lukaseder
[#11614] Fix @Support on ALTER TABLE .. RENAME INDEX
19f0e2b
lukaseder added a commit that referenced this issue Mar 11, 2021
@lukaseder
[#11614] Fix @Support on ALTER TABLE .. RENAME INDEX
52c7701
lukaseder added a commit that referenced this issue Mar 11, 2021
@lukaseder
[#11614] Fix @Support on ALTER TABLE .. RENAME INDEX
451fd38
lukaseder added a commit that referenced this issue Mar 11, 2021
@lukaseder
[#11614] Fix @Support on ALTER TABLE .. RENAME INDEX
757f657
@lukaseder
Copy link
Member Author

Fixed in jOOQ 3.15.0 and 3.14.9 (#11615)

3.13 DDL interpretation automation moved this from To do to Done Mar 11, 2021
lukaseder added a commit that referenced this issue Mar 11, 2021
@lukaseder
[#11614] Fix also the implementation
94aa89b
lukaseder added a commit that referenced this issue Mar 11, 2021
@lukaseder
[#11614] Fix also the implementation
4386235
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: Documentation E: All Editions P: Medium R: Fixed T: Defect
Projects
3.13 DDL interpretation
  
Done
Milestone
Version 3.15.0
Development

No branches or pull requests
1 participant
@lukaseder