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.
before doing a release, we probably want to do this:
accountis one table in the current schema, including three columnswhich 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.