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

DDLDatabase fails when engine=InnoDB is specified #6708

Closed
jkubrynski opened this issue Oct 16, 2017 · 5 comments
Closed

DDLDatabase fails when engine=InnoDB is specified #6708

jkubrynski opened this issue Oct 16, 2017 · 5 comments

Comments

@jkubrynski
Copy link

If an engine is defined for a table DDLDatabase throws C42000_NO_SUBCLASS:

create table test (id bigint) engine=InnoDB;
@lukaseder
Copy link
Member

Thanks for your report. Indeed, these vendor specific storage clauses are currently not parsed correctly as they have no representation in the jOOQ DSL API. I'll look into this ASAP.

@lukaseder
Copy link
Member

This depends on #6131, which I'll implement for 3.11 right now

lukaseder added a commit that referenced this issue Oct 19, 2017
- [#6485] MySQL-specific storage clauses
- [#6708] DDLDatabase fails when engine=InnoDB is specified
@lukaseder
Copy link
Member

Thanks again for your report. This feature has been added to the parser. Unfortunately, as this depends on new API, we can only release the fix in jOOQ 3.11

@lukaseder
Copy link
Member

@jkubrynski Do you have any other similar features that you'd be expecting from the DDLDatabase? Rather than iterating on individual issues over weeks, I'd be happy to implement a bulk of missing features in one go...

@jkubrynski
Copy link
Author

I've already submitted all I had :)

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