-
Notifications
You must be signed in to change notification settings - Fork 515
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
修改了SEQ后没有立即生效 #201
Comments
通过alter sequence语句修改sequence后产生新的版本,但是跟字段关联的sequence却是老版本,所以无法使用新修改的值 问题已修复,感谢报告bug。 |
你是从哪里知道 (next value for myseq) 这种冷门的用法,并且用的还是 system 自动生成的内部 sequence。 |
可以这样改SEQ吗 |
不建议直接使用 system sequence 你可以这样使用: 修改 sequence 只能用 alter sequence myseq restart with 50 information_schema 表是只读的。 |
create table if not exists Seller 我创建表是这样的,然后用Datagrip查询出来的DDL是上面看到的那样子,会自动查询系统自己创建的SEQ |
auto_increment 就对应一个私有的 system sequence,设计的目的就是不能让应用插手。 |
好的谢谢 |
我刚刚新提交了一个代码, |
修改SEQ之后插入还是提示Unique index or primary key violation,需要手动设置一下ID值插入后,自动的才会生效
The text was updated successfully, but these errors were encountered: