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

Comparison with aiosqlite? #1

Open
JWCook opened this issue Dec 21, 2023 · 1 comment
Open

Comparison with aiosqlite? #1

JWCook opened this issue Dec 21, 2023 · 1 comment

Comments

@JWCook
Copy link

JWCook commented Dec 21, 2023

I'm curious about how this differs from aiosqlite. Is it mainly the optional compatibility with trio, or are there other advantages it offers? If so, it might be worth adding a sentence or two about that to the Readme!

Over in aiohttp-client-cache, I've had a few frustrations with aiosqlite, mainly because of its Connection object also being a Thread (see: 187, 189). TL;DR, I'm mainly wondering if the threads managed by anyio are any easier to work with than plain stdlib Thread objects.

@karpetrosyan
Copy link
Owner

karpetrosyan commented Dec 22, 2023

The only difference is that if your Connection is also a Thread, you would manage all of that Thread staff manually, which could cause issues like this whereas in anysqlite, all of that staff is managed by the anyio package, which would not cause your programm to hang indefinitely.

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

No branches or pull requests

2 participants