shared_catalog_product_item doesn't have unique key constraint

[davidtabat]

Please add a unique key constraint to the shared_catalog_product_item table based on sku and customer_group_id:

<constraint xsi:type="unique" referenceId="SHARED_CATALOG_PRODUCT_ITEM_CUSTOMER_GROUP_ID_SKU">
    <column name="customer_group_id"/>
    <column name="sku"/>
</constraint>

This constraint will prevent duplicate entries with the same sku and customer_group_id, which would otherwise cause the PLP to become inaccessible due to an collection error: "Item with the same ID already exists."

[m2-assistant]

Hi @davidtabat. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @davidtabat,

Thank you for your reporting and collaboration.

To speed up the processing of this issue, please provide us with the following information:

Summary of the issue
Information on your environment
Steps to reproduce
Expected and actual results

Thanks.

[engcom-Bravo]

Hi @davidtabat,

This issue is being closed since it has not been updated in a long time.Please feel free to reopen or raise a new ticket if the issue still exists.

Thanks.