You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because the DB is in a cluster configuration it has sql_require_primary_key set to true (not changable), which makes sense in case of replication.
The problem is that a lot of (maybe all of) the magento/openmage indexes create temporary tables without primary keys, triggering errors all over the place (saving products in the backend, reindexing from command line etc).
I'm not that expert in this specific part of the systems so I'm not sure about what I'm writing but... why do you think magento used temporary tables without primary keys? would it be a good thing for use to modify the core to add primary keys to all those tmp tables in order to support this mysql8 cluster thing?
Thanks for any suggestion!
The text was updated successfully, but these errors were encountered:
Hi everybody, I'm trying to use openmage 20.0.7 on a digitalocean stack composed by:
Because the DB is in a cluster configuration it has sql_require_primary_key set to true (not changable), which makes sense in case of replication.
The problem is that a lot of (maybe all of) the magento/openmage indexes create temporary tables without primary keys, triggering errors all over the place (saving products in the backend, reindexing from command line etc).
I'm not that expert in this specific part of the systems so I'm not sure about what I'm writing but... why do you think magento used temporary tables without primary keys? would it be a good thing for use to modify the core to add primary keys to all those tmp tables in order to support this mysql8 cluster thing?
Thanks for any suggestion!
The text was updated successfully, but these errors were encountered: