How can I update my Laravel Eloquent queries to preserve logic after a version change?

The behavior you’re seeing is due to an update in how Laravel’s query builder handles multiple where arrays mixed with orWhere clauses. In newer versions, when you pass entire arrays directly into where() and orWhere(), the logical grouping may not be what you expect.

To achieve your intended logic—namely, grouping all the conditions together like

  (warehouse_id = ? and product_id = ? and section_id = ?)
  OR
  (to_warehouse_id = ? and product_id = ? and section_id = ?)

—you’ll need to use closure groups. For example:

PHPCopied
$transactions = InventoryTransaction::where(function ($query) use ($warehouse, $product, $sectionId) {
    $query->where('warehouse_id', $warehouse->id)
          ->where('product_id', $product->id)
          ->where('section_id', $sectionId);
})->orWhere(function ($query) use ($warehouse, $product, $sectionId) {
    $query->where('to_warehouse_id', $warehouse->id)
          ->where('product_id', $product->id)
          ->where('section_id', $sectionId);
})->get();

This grouping ensures the conditions are evaluated together, which produces the SQL:

SQLCopied
select * from `inventory_transactions`
where (
  (`warehouse_id` = ? and `product_id` = ? and `section_id` = ?)
  or
  (`to_warehouse_id` = ? and `product_id` = ? and `section_id` = ?)
)
and `inventory_transactions`.`deleted_at` is null

What Your Options Are

• Update Your Queries: The recommended approach is to update your code as shown above. Although it may require changes in several places, it makes your queries explicit and aligned with the current behavior of the query builder.
• Sticking With the Old Version: While you can revert to a previous version where the array-based conditions behaved as you expected, doing so will prevent you from taking advantage of future improvements and security updates.

Unfortunately, there isn’t a configuration option to revert the behavior of orWhere. Updating your queries to use closures is the best long‐term solution.

Remember: Whenever you have OR conditions that need to be evaluated together (especially when combined with AND conditions), it’s best practice to group them explicitly with closures to avoid unexpected SQL logic.