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
Microsoft SQL Server doesn't support ORDER in sequences #901
The CREATE SEQUENCE command of Microsoft SQL Server doesn't support the
Therefore, it should be ignored for this DB as well. I have tested this change on an SQL Server 2017 (I had an error with the CREATE SEQUENCE command before, and after applying this and installing to my local Maven repo, the problem was gone).
It would depend on the focus you want to have, I guess. Should it ignore the parameter that it doesn't understand, or should it fail explicitly if there is one? If PostgreSQL fails/checks explicitly, why do MySQL/MariaDB and Sysbase get to ignore it? (there might be a valid reason, I'm just asking
I'm guessing the implications of having an ordered sequence on Oracle become a non-ordered sequence on another DB will be up to each app developer, but I feel that the decision to either fail loudly or ignore the
What I did here was simply "follow" a pattern that I had seen was already present in the code. However, if we have conflicting MOs for this kind of thing, I think it would be a good idea to unify them and just pick one.