PostgreSQL on psycopg 3 (Effect's @effect/sql-pg; the pyfect-dev[pg]
extra, never imported by pyfect).
psycopg's asyncio API runs on a loop thread of its own, so the client works
under run_blocking and run_async and no fiber blocks; interrupting a
statement cancels it in PostgreSQL::
from pyfect.sql import pg
layer = pg.layer(pg.PgPoolConfig(url=redacted.make("postgres://...")))client:PgClient(anSqlClientwithjson,listen,notify),make(pooled),make_client(one session),layer,layer_config,layer_from,make_compilerconnection:PgConnectionsessions (query,query_values,stream,listen,pin,interrupt)pool:PgPoolconfig:PgConnectionConfig,PgClientConfig,PgPoolConfigerror: SQLSTATE classificationmigrator: migrations, withpg_dumpschema dumps
Values are adapted by psycopg (Effect's PgTypes): bytea reads as
bytes, numeric as Decimal, int8 as int, timestamps as
datetime, json / jsonb parsed, enums and unknown types as
str; config.types takes a psycopg AdaptersMap for more, and
psycopg's wrappers (Jsonb, Int4, ...) type a parameter.
Re-exports#
- From
pyfect.sql.pg.client:layer,layer_config,layer_from,make,make_client,make_compiler,PgClient,PgClientService - From
pyfect.sql.pg.config:PgClientConfig,PgConnectionConfig,PgPoolConfig - From
pyfect.sql.pg.connection:DEFAULT_LISTEN_CAPACITY,PgConnection - From
pyfect.sql.pg.pool:PgPool,PgPoolService