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.

Sign up for GitHub

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

ALTER SEQUENCE <seq> START NOT WORKING #7048

Closed
1 task
ghost opened this issue Dec 29, 2016 · 1 comment
Closed
1 task

ALTER SEQUENCE <seq> START NOT WORKING #7048

ghost opened this issue Dec 29, 2016 · 1 comment
Assignees
@luigidellaquila
Labels
bug

Comments

@ghost
Copy link

ghost commented Dec 29, 2016

OrientDB Version, operating system, or hardware.

  • v2.2.14

Operating System

  • Linux

Expected behavior and actual behavior

select from OSequence should show something like this
0 |#7:1|OSequence|100 |1 |100 |ORDERED|pidseq|
the result is that start is set to 0

Steps to reproduce the problem

create sequence pidseq ordered
alter sequence pidseq start 100 increment 1
@luigidellaquila luigidellaquila self-assigned this Dec 29, 2016
@luigidellaquila
Copy link
Member

Hi @austx

Fixed in branch 2.2.x, the fix will be released with 2.2.15

Thanks

Luigi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@luigidellaquila luigidellaquila

Labels
bug
Milestone
No milestone
Development

No branches or pull requests
1 participant
@luigidellaquila