Update tenants.blade.md

This commit is contained in:
Samuel Štancl 2023-01-27 05:17:13 +01:00 committed by GitHub
parent 422ae03911
commit 6d44a86bd9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -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: 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. - 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. - 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.