- last update
over 1 year ago 32 pass - Issue created by @joseph.olstad
- last update
over 1 year ago 32 pass - π¨π¦Canada joseph.olstad
Try this patch instead. This is basically sidestepping with a try catch, I'll worry about this later we weren't even using this module other than it being required by the distro we're using.
- Issue was unassigned.
- Status changed to Postponed: needs info
over 1 year ago 5:27pm 30 July 2023 - π©πͺGermany gbyte Berlin
Not sure what's going on here, but rebuilding the queue during an update is certainly not a good solution. I'll need more reports/eyes on it.
- πΈπ°Slovakia trafo
Updating from 3.10 to 4.1.6:
[notice] Update started: simple_sitemap_update_8401 [error] SQLSTATE[23000]: Integrity constraint violation: 1062 ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '1' for key 'PRIMARY': ALTER TABLE "simple_sitemap" CHANGE `id` `id` INT unsigned NOT NULL auto_increment COMMENT 'Sitemap chunk unique identifier.'; Array()
In my case problem was that there was already sitemap chunk with
id 0
insimple_sitemap
table.Solution could be just simply delete all records with
\Drupal::database()->query('DELETE FROM {simple_sitemap}');
.
Other possibility would be update withMAX(id) + 1
- Status changed to Closed: cannot reproduce
about 1 month ago 8:00pm 11 October 2024 - π©πͺGermany gbyte Berlin
There seems to be a rare problem with changing the sitemap ID column to serial in simple_sitemap_update_8401 and having data in that table. Since apparently this is so anecdotal and spinning up an ancient D8 instance is a bit of an inconvenience, I'm just going to close this issue as not reproducible. If you are a snowflake and encounter this, try and empty the simple_sitemap table and run the updates again.