MySQL foreign key constraint scenarios silently in Laravel with composite keys
Does anyone know how to I'm having a hard time understanding I'm working with an scenario with MySQL foreign key constraints in a Laravel application... I have two tables, `orders` and `order_items`, where `order_items` references a composite key in `orders`. My `orders` table has a primary key composed of `order_id` and `customer_id`, and I want to enforce that each `order_item` references a valid `order`. Here are the relevant migration files: **Orders Migration:** ```php Schema::create('orders', function (Blueprint $table) { $table->unsignedBigInteger('order_id'); $table->unsignedBigInteger('customer_id'); $table->primary(['order_id', 'customer_id']); $table->timestamps(); }); ``` **Order Items Migration:** ```php Schema::create('order_items', function (Blueprint $table) { $table->unsignedBigInteger('order_id'); $table->unsignedBigInteger('customer_id'); $table->foreign(['order_id', 'customer_id'])->references(['order_id', 'customer_id'])->on('orders')->onDelete('cascade'); }); ``` I've confirmed that both columns in the `order_items` table match the types and constraints of the `orders` table. However, when I attempt to insert a new record in `order_items`, I don't get any errors, but the record is silently ignored, and nothing is inserted into the database. I've also checked the database for existing records and confirmed that an `orders` record with the provided `order_id` and `customer_id` does exist. I tried disabling `foreign_key_checks` in MySQL but then received the behavior about foreign key constraints when re-enabling it, which indicates that the underlying scenario is likely with the constraint definitions. Can anyone provide insights on why this might be happening or suggest how I can debug this further? I'm using MySQL 8.0 and Laravel 9.x. Thanks in advance! This is part of a larger web app I'm building. What are your experiences with this? I'm working in a Ubuntu 20.04 environment. Thanks for any help you can provide!