Skip to content
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.

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

Serializable Isolation level for SQLite Databases #4536

Open
ClaudeTO80 opened this issue Apr 22, 2024 · 1 comment
Open

Serializable Isolation level for SQLite Databases #4536

ClaudeTO80 opened this issue Apr 22, 2024 · 1 comment
Labels

Comments

@ClaudeTO80
Copy link

Hi all.

I am working on a personal project using DB connection both to SQLite and PostgreSQL. Due to nature of some insert statements, serializable transactions are required.

As far as I understood by reading Poco source code, PostgreSQL session implementation handles all kinds of transactions, while SQLite session implementation handles only Read committed one.
Moreover I read SQLite project documentation and it seems (if I didn't misunderstood) that SQLite handles serializable transactions if proper compile-time and run-time options are used.

I was wondering:

  1. if limitations to SQLite transactions in Poco library are due to historical or security reasons
  2. should it be possible handling all types of transactions in SQLite session implementation?

Thanks in advance.
Best things.

@aleks-f
Copy link
Member

aleks-f commented May 13, 2024

As far as I can remember, the reason for weaker transaction support in SQLite is because nobody so far had a need for those. I see no reason why it shouldn't be supported, but I can't promise when that would be done; you can do the work yourself and send pul request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants