Skip to content

Conversation

@markhobson
Copy link

Addresses #95 by adding a storage backend for native SQLAlchemy rather than Flask-SQLAlchemy. Based off the existing Flask-SQLAlchemy backend implementation.

Submitted for early feedback, so no docs yet. Interested in:

  • whether this backend would be considered
  • a better naming strategy (should sqlalchemy be renamed to flask_sqlalchemy?)
  • the general approach

Happy to refine further if welcome.

@ddorian
Copy link

ddorian commented Aug 16, 2024

I would generally prefer data to be in a json(b) column so it's easy to query and read. Think find/delete all sessions of a user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants