Viewing profile — dvarrazzo

Psycopg 3 supports both sync and async code. Starting from release 3.2, the sync side is automatically generated from the async counterpart. This article explains how it's done, an…

As someone who is trying to make a living out of free software, I would love to see this project succeeding. The other remotely similar service, Tidelift, has unacceptable terms an…

This is interesting, thank you for pointing it out. Worth looking if the problems can be fixed the same way in both the adapter (and probably everything else using server-side bind…

There is a mechanism to ensure that there is no unexpected regression. Exposing the PSYCOPG_IMPL env var a program can make sure to obtain a specific implementation and import fail…

> You can put comments in Python files... only if the comment pertains to a django feature, not to a schema feature that cannot be expressed in django (e.g. a partial index designe…

It also breaks in interesting way: I discovered just today that constants defined on the Model subclass are not available when you use 'get_model()'. I suspect methods wouldn't be …

My strategy here is to have a staging server where migrations are applied before they can hit production. As someone else pointed out, migration without CI can be dangerous and dif…

Hi! Much of the difficulty comes from using blocking libpq calls in psycopg2. I'm thinking to avoid them altogether in psycopg3 and only use async calls with Python in charge of bl…