Many to many associations on versioned entites (specifically order tags) are not really versioned

[nickygerritsen]

PHP Version: 8.2 | Shopware Version: 6.6.9.0 | Affected area / extension: Platform(Default)

---

Actual behaviour:

Order has a many to many association with tags through the OrderTagDefinition definition.
That definition has an order version ID (but not it's own version ID).

However, when creating a version of the order, we do not copy the data from the order_tag table, because it is not marked as cascade delete (and I don't think it should?) and thus it is not added as a clone assocation. And because there is no version_id column we also don't add any version query information to the select query.

So:

• It seems currently order_version_id is not really used in order_tag. Should it?
• Should order_tag have a version_id column as well?
• Should data from the order_tag table be copied when creating a new version of an order?

Or are tags on orders not versioned on purpose? Currently if you create an order with tags, create a new version of that order and remove tags from that version, the tags are also gone on the original order.

Expected behaviour:

I expect the version logic of order tags to either use the order version ID or the order version ID to be dropped from the table if it's not used anyway.

How to reproduce:

• Create an order with tags.
• Create a new version of that order.
• Remove a tag from that version.
• Load the original order version.
• Inspect that the tag is also gone on that version of the order.

[shopwareBot]

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-40266

[created from NEXT-40266, comment 533939]

[shopwareBot]

[public]

Priority changed to: Low

Thank you for your report. After careful consideration, we've concluded that this issue does not require immediate attention or isn't something we can address right now. We prioritize openness and clear communication with our community, so we want to be transparent. We may not resolve all reported issues, and this one might remain unresolved. To stay effective, we periodically clean our backlog, and this issue could be closed in the future.

For now, we'll keep this ticket open to invite further feedback from the community in case we've underestimated its impact and to allow us to revisit it later.

[created from NEXT-40266, comment 533956]