Closed Hocdoc closed 7 years ago
Hello @Hocdoc,
This error can happen when you have 2 completeness calculations executed at the same time on the same product. For instance, if you run a product export while a completeness command is also being launched, it creates a conflict and such issues happen.
I'm not sure how you or we can prevent that.
Best regards,
Laure
Thanks, this is a good explanation. There were some mass edits in the same time, maybe they have triggered the completeness calculation.
The error may be prevented when using an INSERT IGNORE
instead of the INSERT
SQL command (found in CompletenessGenerator.php
)? Should I write a PR?
Hello @Hocdoc,
Thanks for your feedback, we'll be very pleased if you could :) Our core team will review it and let you know if it's accepted or not. Thanks a lot for contributing :)
Kind regards,
Laure
Hi @Hocdoc, thanks again for contributing! Your fix has been merged in the next coming version. Can we close this issue?
Kind regards,
Laure
When we export our 160,000 products with Akeneo 1.5.5/MySQL we sometimes get this exception during the job execution:
Wow, that's really a big SQL statement :-o. You have to scroll to the right to see the error message:
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1-1-161126' for key 'searchunique_idx'
.Anything we can do?