Laravel DatabaseTransactions do not work with DB Facade

Asked Mar 28 '19 at 10:08

Active May 08 '19 at 02:30

Viewed 969 times

I have an issue when I run tests using DatabaseTransactions. In my Products table, I have all Products where the stock_count = -99.

Here is my code

TestCase.php (all the tests extend this class)

use DatabaseTransactions;

protected $connectionsToTransact = ["mysql"];

public function setUp()
{
   parent::setUp();
   MimProduct::query()->update(['stock_count'=>100]);
   ...
}

Then in one of my test, I dd the same query, one using DB Facade the other one using the actual model.

 dd(DB::table("mim.products")->first(),MimProduct::all()->first());

and the output is

My conclusions so far are:

Using the DB facade doesn’t work with the DB Transaction trait; it cannot use the “in-memory” transactions, and so it will work off the “live” DB.
Whereas a model has access to memory.

Am I correct or there is a way to overcome this issue?

edited May 08 '19 at 02:30

Karl Hill

12,937
5
58
95

asked Mar 28 '19 at 10:08

Alessandro.Vegna

1,262
10
19

What's the default connection for your tests? – Jonas Staudenmeir Mar 28 '19 at 22:23
The default connection is mysql – Alessandro.Vegna Apr 01 '19 at 08:37
Your model uses the `mim` connection which is missing from `$connectionsToTransact`. `DB::table("mim.products")` uses the default `mysql` connection. – Jonas Staudenmeir Apr 01 '19 at 08:58
I tried as well to put both of the connections in $connectionsToTransact but it did not work, at the end I got rid of "mim" connection and use only the "mysql" and everything worked, it's not a proper solution but better than nothing. Thanks tho] – Alessandro.Vegna Apr 01 '19 at 14:05

Laravel DatabaseTransactions do not work with DB Facade

0 Answers0