You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently do not have any way to alter sequence flags, except for the START WITH flag, which can be reset using ALTER SEQUENCE .. RESTART WITH or ALTER SEQUENCE .. RESTART.
Oracle, for example, supports this syntax:
We should allow for altering the following flags as well:
INCREMENT BY
MAXVALUE
MINVALUE
CYCLE
CACHE
PostgreSQL has no NO CACHE clause and thus requires a CACHE 1 clause instead.
Looking at AlterSequenceStep it strikes me as slightly odd that it has a generic type parameter <T extends Number>. To be consistent with the CreateSequenceFlagsStep API, I would propose to remove that generic type parameter. This would however not be a source compatible change (or is the assignment of Step APIs exempt from our source compatibility rules?), which isn't nice.
Adds the new `AlterSequenceFlagsStep` as a supertype to
`AlterSequenceStep`, which allows setting and clearing various flags
like `MINVALUE` and `CACHE`.
Using generics here causes problems given the current signatures on
`DSLContext`, where the return type explicitly uses `BigInteger` as the
generic type parameter.
We currently do not have any way to alter sequence flags, except for the
START WITH
flag, which can be reset usingALTER SEQUENCE .. RESTART WITH
orALTER SEQUENCE .. RESTART
.Oracle, for example, supports this syntax:
We should allow for altering the following flags as well:
INCREMENT BY
MAXVALUE
MINVALUE
CYCLE
CACHE
NO CACHE
clause and thus requires aCACHE 1
clause instead.ORDER
(see Support CREATE SEQUENCE ... [ [ NO ] ORDER ] #9346)The text was updated successfully, but these errors were encountered: