Percona-XtraDB-Cluster doesn't recommend use of DML command on a table (mshop_index_supplier)

[kopz]

Hi,

Any reason why some tables don't have a primary key (mshop_index_price, mshop_index_supplier ...) ? I'd just like to know if I can safely make migrations on these tables to alter prodid into PK without any side effects.

{"log":"2024-11-13T09:21:08.071343Z 38589 [Warning] [MY-000000] [WSREP] Percona-XtraDB-Cluster doesn't recommend use of DML command on a table (b2bshop.mshop_index_supplier) without an explicit primary key with pxc_strict_mode = PERMISSIVE\n","file":"/var/lib/mysql/mysqld-error.log"}

[aimeos]

The index tables doesn't need primary keys and you can't add primary keys to existing columns as this will likely lead to insert errors during index rebuild.

[kopz]

you can't add primary keys to existing columns

What about adding a new column (PK AI) without altering any of the existing columns?

Thanks for the answers.

[aimeos]

Would be superfluous because it would be not used at all. Remember that this is only a recommendation which is not necessary or helpful in that case. When does it appear in the logs? When you run the migration tasks?