Laravel conflicts with Percona DB because of tables without Primary Keys

Asked Mar 05 '20 at 14:03

Active Mar 05 '20 at 14:03

Viewed 785 times

Laravel has 2 tables (migration, password_resets) that don't have PK and is causing problems with Percona DB. My current fix to this is to set Percona into:

  SET GLOBAL pxc_strict_mode=PERMISSIVE;

Error:

  SQLSTATE[HY000]: General error: 1105 Percona-XtraDB-Cluster prohibits use of DML command on a table (tt.password_resets) without an explicit primary key with pxc_strict_mode = ENFORCING or MASTER

Though I'm not sure if this is the best approach for this.

What should be the best approach to handling this scenario or what I'm doing is already acceptable?

asked Mar 05 '20 at 14:03

magicianiam

1,474
7
33
70

Can't you just edit the migration and add a primary key? – Anas Bakro Mar 05 '20 at 14:36
considering that's a laravel default table, I'm not sure that's is such a good idea – magicianiam Mar 05 '20 at 15:03
It's the password reset table, go ahead and add a primary key. Won't affect the queries. – IGP Mar 05 '20 at 17:12
@IGP same for the migration table? – magicianiam Mar 06 '20 at 06:25
Should be the same. – IGP Mar 06 '20 at 13:49

Laravel conflicts with Percona DB because of tables without Primary Keys

0 Answers0