New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature parity between PostgreSQL and SQLite backends #6435

Open

5 of 7 tasks

danielhollas opened this issue May 31, 2024 · 0 comments

Labels

topic/database-backend topic/storage type/feature request

Collaborator

danielhollas commented May 31, 2024 •

edited

Loading

This is a tracking meta issue for collecting known functional differences between the two DB backends.

Tasks

Beta Give feedback

🐛 Strange behavior for !has_key filter with SQLite storage backends #6256

topic/query-builder topic/storage type/bug
SqliteDosStorage: Make the migrator compatible with SQLite #6429
[devops] Run tests with sqlite backend #6425
test_delete_through_backend fails with SQLite: sqlalchemy.orm.exc.ObjectDeletedError #6436

priority/important topic/database-backend type/bug
QueryBuilder: 'contains' operator not implemented for SQLite storage backends #6494

topic/database-backend topic/storage type/feature request
QueryBuilder: implement the has_key operator properly for SQLite based storage plugins #6498

topic/query-builder type/feature request
Reimplement has_key for SQLite #6552

topic/storage type/feature request
Options

The text was updated successfully, but these errors were encountered:

danielhollas added the type/feature request label

agoscinski added topic/storage topic/database-backend labels

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