Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Here are these flags:
Once we have these flags, they need to be:
Looking at the interfaces which describe the information schema (
Number getStartWith(); Number getIncrementBy(); Number getMinValue(); Number getMaxValue(); Boolean isCycle(); Number getCache();
@lukaseder: 1) We can replace all
Trying to devise this API raised a few questions, which I think need to be discussed:
@lukaseder What is your take on this?
Yes, correct, that is the historic convention in the jOOQ API, which mixes meta data navigation and DSL:
Having said so...
I think we should use the alternative
I'm not sure if we already have a precedent for a boolean value in the meta APIs...
I will comment to your various bullets directly inline, by editing your comment.
Yes of course! All representations of
Yes, sure. A separate issue is fine.
So in summary you propose to:
Yes, it makes sense anyway. The
Sure we can do that for now.
We generally don't do that as there's always one RDBMS that does support arbitrary
We shouldn't limit our main product offering (generic DSL, parser, etc.) because one of our features (interpreter) cannot handle the entirety of possible use cases (yet). We can throw a meaningful error message in case a non-
Notice that there are a few other types of
Adds the following methods to the `Sequence` interface: `getStartWith()`, `getIncrementBy()`, `getMinValue()`, `getMaxValue()`, `getCycle()`, and `getCache()`. The `Sequence` objects returned by the `DDLInterpreter` now return the expected values when these methods are called. And `DDL` (aka `DSLContext#ddl()`) queries these methods to create a corresponding `CREATE SEQUENCE` query.