Fix: migrate users.hashed_password to nullable for OIDC user creation#91
Merged
Conversation
hunter-read
deleted the
90-oidc-error-voidauth-sqlite3integrityerror-not-null-constraint-failed-usershashed_password
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Existing deployments had hashed_password NOT NULL (pre-OIDC schema). SQLAlchemy's create_all doesn't alter existing tables, so OIDC auto-register failed with an IntegrityError when creating passwordless users. Adds a startup
migration that detects the constraint via PRAGMA table_info and recreates the users table using SQLite's copy-rename pattern to drop it.
Type of change
Testing
pytest -q)npm test)