Changes between Version 1 and Version 2 of Ticket #28272
- Timestamp:
- Jun 4, 2017, 8:30:40 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #28272 – Description
v1 v2 24 24 In my opinion, the sequence attached to the primary key should be manually set to the next available PK after inserting an object with an explicitly specified PK (e.g. using setval [2]). The same issue can be observed for {{{bulk_create}}}, where I think the highest primary key of the batch should be used to determine the next value in the DB sequence. 25 25 26 MariaDB [3] and SQLite [4] update the next value in the sequencewhen autoincrement is used.26 MariaDB [3] and SQLite [4] update the next value correctly when autoincrement is used. 27 27 28 28 Oracle might be also be affected by this issue. I was able to find this old ticket on the bug tracker[5].