Support for psycopg3

[elderlabs]

Preemptive ticket here. The maintainer of psycopg2 has busied themself with its next iteration, psycopg3. Are there plans to add support for the project; is there already native support by design? This ticket's more to see if the project's on your radar as it has officially released, and support for psycopg2 might be in decline fairly soon.

Thanks.

[coleifer]

There are a number of psycopg3 changes that look to be backwards-incompatible (which is understandable) but will likely be a pain to identify and work around. Parameter binding, especially, looks like it has changed quite a bit.

It's definitely on my radar and will be added to Peewee, but I will probably wait a bit to add support. If anyone is interested in the meantime, feel free to implement this in a standalone/extension module.

[MaartenUreel]

Hello

I looked at your extension but I wondering, can I use this in conjuction with PostgresqlExtDatabase?

Any plans on built-in support for psycopg3? Considering is also adding it in their next release and it is a stable release..

[coleifer]

Are there any specific features of PostgresqlExtDatabase you were intending to use - e.g. jsonb, arrays? I'll have to spend some time seeing what works and what doesn't, since we use some helpers from psycopg2.extras (e.g. Json).

[MaartenUreel]

I'm going through all my raw SQL code currently, but if I'm not mistaken I will have some jsonb-specifics.

I will use psycopg2 for now though, but it would be great to see support for 3.

[coleifer]

No, I agree with you, things are going to be moving towards psycopg3 in the coming years so I'll want to be ready for that. Thanks for the ping on this, I'll be aiming to getting parity for psycopg3 with the current PostgresqlExtDatabase. No definitive timeline but it's a priority for me.

[amirreza8002]

hello
so i'm wondering if there are any news on this?

[coleifer]

Merged into master.

[HammerMeetNail]

@coleifer Great to see this merged. When do you think a release will be cut?

[andrewchen5678]

it is not merged to master yet, I just checked master and it is still have the hard coded check for psycopg2 for postgres, which is not the right package for psycopg3. The right package for psycopg3 is psycopg without 2. Please reopen this ticket.

    def _connect(self):
        if psycopg2 is None:
            raise ImproperlyConfigured('Postgres driver not installed!')

[coleifer]

The standard PostgresqlDatabase will continue to use psycopg2 for the foreseeable future. To use psycopg3, use playhouse.psycopg3_ext.Psycopg3Database.

[harishvadali]

@coleifer Thank you for adding the psycopg3 support. I see the field for BinaryJSONField but not JSONField with psycopg3. Is that on roadmap?

[coleifer]

Is there a compelling reason not to use jsonb?