From 9003b7ab163215bd06716a9277c5f37d2ed6a17f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Samuel=20=C5=A0tancl?= Date: Mon, 3 Jan 2022 23:57:46 +0100 Subject: [PATCH] 3.5.0 queue changes --- source/docs/v3/queues.blade.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/source/docs/v3/queues.blade.md b/source/docs/v3/queues.blade.md index 16fd4ef..a299c08 100644 --- a/source/docs/v3/queues.blade.md +++ b/source/docs/v3/queues.blade.md @@ -10,8 +10,6 @@ If you're using the `QueueTenancyBootstrapper`, queued jobs dispatched from the **However**, note that if you're using the `DatabaseTenancyBootstrapper` and the `database` queue driver, or the `RedisTenancyBootstrapper` and the `redis` queue driver, you will need to make sure the jobs don't get dispatched into the tenant context for these drivers. -Note: You cannot inject model **instances** with the `SerializesModels` trait, because it tries to hydrate the models before the `tenant` connection is created. Inject model ids instead and use `find()` in the handle method. - ### Database queue driver {#database-queue-driver} To force the database queue driver to use the central connection, open your `queue.connections.database` config and add the following line: