split up `account` table in `basic_auth_schema.sql`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 838
- Forks
- 123
- Avg merge
- 7h 58m
- Merged PRs (30d)
- 12
Description
before doing a release, we probably want to do this:
account is one table in the current schema, including three columns
username VARCHAR NOT NULL,
email VARCHAR NOT NULL,
password_blob VARCHAR NOT NULL,
which are not required for all applications, and are in fact not really best practice for most applications these days.
Before we commit to this schema as a mechanism that applications start depending on with not much of a schema migration path, perhaps usernames, passwords, and email addresses should be split out into separate tables, so that we don't require that klein applications authenticate with passwords.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading basic_auth_schema.sql and tracing how the current account table is used by the schema and authentication code. Clarify the migration and compatibility requirements before defining separate handling for usernames, email addresses, and passwords, with completion meaning applications are not forced to use password authentication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100