Support for Percona XtraDB Cluster with Strict Mode Enabled

[philipkozeny]

Percona XtraDB Cluster is a widely-used MySQL Galera Cluster solution, recommended for production environments. When operating in its recommended strict mode for production use, the cluster mandates that all tables must have an explicit primary key.

While attempting to run Telescope on a Percona XtraDB Cluster with strict mode enabled, the following error occurs:

SQLSTATE[HY000]: General error: 1105 Percona-XtraDB-Cluster prohibits use of DML command on a table (citizen.telescope_entries_tags) without an explicit primary key with pxc_strict_mode = ENFORCING or MASTER (Connection: mysql, SQL: insert into `telescope_entries_tags` (`entry_uuid`, `tag`) values (9a031faf-ad80-454a-9535-4222cc3658e8, slow))

[github-actions]

Thank you for reporting this issue!

As Laravel is an open source project, we rely on the community to help us diagnose and fix issues as it is not possible to research and fix every issue reported to us via GitHub.

If possible, please make a pull request fixing the issue you have described, along with corresponding tests. All pull requests are promptly reviewed by the Laravel team.

Thank you!

[driesvints]

I'm sorry but I don't think we can account for this edge case. Since we only have one report so far and the ticket has been open for a while I'm going to close this one.

[zoispag]

Hi @driesvints. I like to add to this issue; I have been considering an HA MySQL solution, and both Percona XtraDB (Galera) as well as the Oracle MySQL Operator (Group replication) use replication, which requires primary keys to exist on all tables. Currently this limits HA MySQL deployments. Therefore, I don’t think it’s an unreasonable request, nor an edge case.

Can we reopen this issue so it can addressed?

[driesvints]

I'm sorry but no. We are open to PRs however.