Glyph

Thanks for filing this, and the upstream ticket.

Changing the name on this issue because although txpostgres may well satisfy the goal, so might https://magicstack.github.io/asyncpg/ or https://pypi.python.org/pypi/aiomysql/ or http://aiopg.readthedocs.io/en/stable/ - alchimia should probably be able to work with...

Also, I should note: now that the main entrypoint into the library is `wrap_engine` we can have a clean break for native-async stuff and just have an `async_engine` function that...

@dpnova @graingert Anyone feel like wrapping one of these up into a PR? :)

> IIRC, according to @glyph, the issue here is that SQLite doesn't work at all with Alchmia, because SQLite doesn't get along with multiple threads. Wait, what? SQLite works fine...

> So… either Alchmia should prevent the use of threads when one is using SQLite, or, the example code on the `README` file should stop using SQLite as an example,...

@iffy It's been a while! I'm not sure if you're still interested in this. But there's a new (private, for now) API in Twisted which may be promising for this...

@iffy - I actually have an implementation on https://github.com/glyph/alchimia right now, which I hope to integrate and release in the coming week :). It's untested right now, or rather, it's...

@hawkowl No, because we still haven't dealt with the issue of a `Deferred`-aware pool. The current strategy, while more correct, is less efficient. It opens a new thread for every...

Yeah, so, it looks like with sqlite it selects the "null pool" http://docs.sqlalchemy.org/en/rel_1_1/dialects/sqlite.html?highlight=sqlite#threading-pooling-behavior - perhaps we should somehow force this to happen with any other database adapters as well, until...