[–] sdrothrock 6y ago ↗ I read this and my first question was "Why?"He has a previous post titled "Thinking psycopg3" that shed some light on the issue: https://www.varrazzo.com/blog/2020/03/06/thinking-psycopg3/- Query parameters adaption- Context managers and transactions- Optional C module (i.e. reduce requirements)- Async from the ground up- Resolve other outstanding issuesReading that post first went a long way toward giving me some context to understand this one. [–] OldTechSucks 6y ago ↗ Just use SqlAlchemy :)) the post doesn't make any sense [–] Spiritus 6y ago ↗ What are you talking about? What do you think SQLAlchemy uses as a Postgres driver?Sure, there's some alternatives. But 99% use psycopg2.
[–] OldTechSucks 6y ago ↗ Just use SqlAlchemy :)) the post doesn't make any sense [–] Spiritus 6y ago ↗ What are you talking about? What do you think SQLAlchemy uses as a Postgres driver?Sure, there's some alternatives. But 99% use psycopg2.
[–] Spiritus 6y ago ↗ What are you talking about? What do you think SQLAlchemy uses as a Postgres driver?Sure, there's some alternatives. But 99% use psycopg2.
3 comments
[ 3.5 ms ] story [ 13.1 ms ] threadHe has a previous post titled "Thinking psycopg3" that shed some light on the issue: https://www.varrazzo.com/blog/2020/03/06/thinking-psycopg3/
- Query parameters adaption
- Context managers and transactions
- Optional C module (i.e. reduce requirements)
- Async from the ground up
- Resolve other outstanding issues
Reading that post first went a long way toward giving me some context to understand this one.
Sure, there's some alternatives. But 99% use psycopg2.