Tiago Silva

> Yes, this also fixes the bug that would report multiple primary keys if the user-defined primary key field had a name other than id. > > You can add...

> If the user creates the model with an id for the primary key name then everything works fine. Using a different name will result in the following error. >...

@ansipunk psycopg3 is called simply psycopg. https://pypi.org/project/psycopg/ This version is already being supported.

@ansipunk got it. We are talking 2 completely different things. You meant the scheme support. Why is that needed? Normally postgres or asyncpg would suffice as internally is converted. What...

@ansipunk ok, let's start over. Apologies if I'm lost here. Internally uses asyncpg and aiopg yes for async driver but here https://github.com/encode/databases/blob/master/databases/backends/postgres.py it uses the SQL alchemy 2 dialect for...

> The use case is to use `psycopg` instead of `asyncpg`. With `asyncpg` we have to have `psycopg` anyway for `SQLAlchemy-Utils` and `alembic` to function. With this working we can...

@devkral the release branch no longer exists, he should try the main

This is pending

@zevisert good question. I need to have a look and come back to you. Thank you for tagging me on it. @devkral can we run some tests and check this,...

@zevisert i can see I your example that you want to use different connections? We have something similar with the "using" and "using_with_db" operations on a queryset. We don't share...