From b62e2535c2bd821ecf6f9a45a2765ba699d4133a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Samuel=20=C5=A0tancl?= Date: Thu, 12 Nov 2020 14:01:54 +0100 Subject: [PATCH] Generating global ids --- source/docs/v3/synced-resources-between-tenants.blade.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/docs/v3/synced-resources-between-tenants.blade.md b/source/docs/v3/synced-resources-between-tenants.blade.md index c547011..f028db9 100644 --- a/source/docs/v3/synced-resources-between-tenants.blade.md +++ b/source/docs/v3/synced-resources-between-tenants.blade.md @@ -213,10 +213,12 @@ Attaching a tenant to a user will copy even the unsynced columns (they act as de If you'd like to use a custom pivot model, look into the source code of `TenantPivot` to see what to copy (or extend it) if you want to preserve this behavior. +Also note that if you create a user in the tenant's database, the global id will be created using the ID generator. If you disable the ID generator for [incrementing tenant ids]({{ $page->link('tenants') }}#incrementing-ids), you'll need to make some changes. + ## Queueing {#queueing} In production, you're almost certainly want to queue the listener that copies the changes to other databases. To do this, change the listener's static property: ```php \Stancl\Tenancy\Listeners\UpdateSyncedResource::$shouldQueue = true; -``` \ No newline at end of file +```