fix: Handle username UNIQUE constraint in SaaS user provisioning #19

Merged
nrupard merged 1 commit from fix/db-error into main 2026-03-25 16:20:21 +01:00
Member

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>
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>
nrupard deleted branch fix/db-error 2026-03-25 16:20:21 +01:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
a8n-tools/rus!19
No description provided.