fix: Handle username UNIQUE constraint in SaaS user provisioning #19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/db-error"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Use UPDATE-first strategy to avoid UNIQUE constraint failure on
users.username when provisioning existing SaaS users. For new users,
fall back to saas_{id} username if email-derived name is already taken
by a different user.
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
Use UPDATE-first strategy to avoid UNIQUE constraint failure on users.username when provisioning existing SaaS users. For new users, fall back to saas_{id} username if email-derived name is already taken by a different user. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>