From 6d44a86bd90cf40d25f20fb78cb9f0f5799628fd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Samuel=20=C5=A0tancl?= Date: Fri, 27 Jan 2023 05:17:13 +0100 Subject: [PATCH] Update tenants.blade.md --- source/docs/v3/tenants.blade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/docs/v3/tenants.blade.md b/source/docs/v3/tenants.blade.md index 38704bd..6985d1c 100644 --- a/source/docs/v3/tenants.blade.md +++ b/source/docs/v3/tenants.blade.md @@ -12,7 +12,7 @@ The package comes with a base `Tenant` model that's ready for common things, tho The base model has the following features on top of the ones that are necessary by the interface: -- Forced central connection (lets you interact with Central models even in Tenant contexts) +- Forced central connection (lets you interact with `Tenant` models even in the tenant context) - Data column trait — lets you store arbitrary keys. Attributes that don't exist as columns on your `tenants` table go to the `data` column as serialized JSON. - Id generation trait — when you don't supply an ID, a random uuid will be generated. An alternative to this would be using AUTOINCREMENT columns. If you wish to use numerical ids, change the `create_tenants_table` migration to use `bigIncrements()` or some such column type, and set `tenancy.id_generator` config to null. That will disable the ID generation altogether, falling back to the database's autoincrement mechanism.