The readme advertises that Chancy's psycopg3 dependency can be installed alongside psycopg2:
Minimal dependencies - Core functionality requires only psycopg3 - which can be installed side-by-side with psycopg2.
This is exciting because it allows usage on legacy projects that may have dependencies on old versions of sqlAlchemy and/or psycopg.
However: Chancy's _ex interfaces currently seem to require psycopg3 cursors -- which limits interactions from legacy code. I'm especially interested in: push_ex, push_many_ex, and sync_push_many_ex which would be used to support a key function: the ability to use Chancy as a transactional outbox (from legacy code).
For ease of compatibility on projects that currently use psycopg2, it may be useful to provide interfaces that can take a psycopg2 cursor optionally instead of a psycopg3 cursor.
I'm curious if there is interest in providing such a compatibility layer.
The readme advertises that Chancy's psycopg3 dependency can be installed alongside psycopg2:
This is exciting because it allows usage on legacy projects that may have dependencies on old versions of sqlAlchemy and/or psycopg.
However: Chancy's
_exinterfaces currently seem to require psycopg3 cursors -- which limits interactions from legacy code. I'm especially interested in:push_ex,push_many_ex, andsync_push_many_exwhich would be used to support a key function: the ability to use Chancy as a transactional outbox (from legacy code).For ease of compatibility on projects that currently use psycopg2, it may be useful to provide interfaces that can take a psycopg2 cursor optionally instead of a psycopg3 cursor.
I'm curious if there is interest in providing such a compatibility layer.