Skip to content

IBX-10685: Fixed schema metadata duplication#34

Closed
reithor wants to merge 1 commit into4.6from
ibx-10685_allowed-shared-metadata
Closed

IBX-10685: Fixed schema metadata duplication#34
reithor wants to merge 1 commit into4.6from
ibx-10685_allowed-shared-metadata

Conversation

@reithor
Copy link

@reithor reithor commented Oct 22, 2025

🎫 Issue IBX-10685

"By design" we allow multiple attributes/gateways per table for custom product attributes (see https://doc.ibexa.co/en/4.6/pim/create_custom_attribute_type/ where Attribute\Float\StorageSchema is used for a custom attribute).

@reithor reithor marked this pull request as ready for review October 22, 2025 13:47
@reithor reithor requested review from a team and Steveb-p October 22, 2025 13:47
@ezrobot ezrobot requested review from ViniTou, adamwojs, alongosz, barw4, ciastektk, konradoboza, mikadamczyk, tbialcz and wiewiurdp and removed request for a team October 22, 2025 13:49

$tableName = $metadata->getTableName();
if (isset($this->tableToMetadata[$tableName])) {
if (isset($this->tableToMetadata[$tableName]) && $this->tableToMetadata[$tableName] != $metadata) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To put it simply, if two metadata services exist for the same table (even if they have the exact same properties), that is an error and shall not be ignored :)

The error should be found and removed, not silently ignored.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Steveb-p so we need to fix it in https://github.com/ibexa/product-catalog/ somehow ? Should i close this PR ?

@reithor
Copy link
Author

reithor commented Oct 23, 2025

closed - as issue likely need to be fixed in https://github.com/ibexa/product-catalog/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants