There seems to be an error after updating from 2.36 to 2.38. Is there any workaround...?
Drupal\Core\Database\IntegrityConstraintViolationException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'commerce.8203' for key 'PRIMARY': INSERT INTO "commerce_inbox_message" ("id", "subject", "message", "cta_text", "cta_link", "send_date", "state") VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6); Array ( [:db_insert_placeholder_0] => commerce.8203 [:db_insert_placeholder_1] => Introducing the Commerce Dashboard [:db_insert_placeholder_2] => Commerce Core 2.37 introduced a new dashboard to Drupal Commerce. Designed with merchants in mind, it includes easy access management links, sales metrics and summary reports, and project updates in the form of a "Commerce inbox." Future releases will build on this work to give you even greater insight into your store's performance. [:db_insert_placeholder_3] => [:db_insert_placeholder_4] => [:db_insert_placeholder_5] => 1709818928 [:db_insert_placeholder_6] => unread ) in Drupal\mysql\Driver\Database\mysql\ExceptionHandler->handleExecutionException() (line 50 of /home/zuginawu/public_html/commerce.mazzedev.ch/web/core/modules/mysql/src/Driver/Database/mysql/ExceptionHandler.php).
Fixed
2.38
Other
Really not sure what would cause this? Especially since we're making a merge query from InboxMessageStorage::save() which should update the message and not perform an insert.
Also how is it that you already have a message? I guess what you could do is removing the message from the database? The DB table is "commerce_inbox_message".
Automatically closed - issue fixed for 2 weeks with no activity.