Feature Request: Middleware

Nessuno ha ancora preso questa issue.

As discussed in #128, it might be a cool idea to have a "middleware" layer in asyncpg where people can register their own code to be ran pre or post query.

One usecase is asyncpgsa, which is a project to allow sqlalchemy objects to be passed to asyncpg connection methods. If there was a middleware layer, asyncpgsa could simply be a middleware that would run right before asyncpg prepared the query to convert the sqlalchemy object into a string. This would make asyncpgsa stupid simple, and just be a conversion layer, allowing it to get out of the way, and let asyncpg be the source of truth for everything else.

Another use case is metrics. My org is starting to track metrics per endpoint and per database query. If asyncpg had middleware support, we could simply inject a middleware that tracked the query and the time it took, and send that information into our metric platform. This could be done today by wrapping asyncpg and adding a method around it that tracks the metrics. It would be amazing if instead asyncpg could be used directly, and the middleware handles that portion for me.

Middlewares could potentially be "added" when the pool is created. (they can only exist on a pool maybe?)

Anyways, I am happy to try to implement this if you would like, but first wanted to get a general discussion going on the topic.

Leggi prima l’issue #128, poi esamina la creazione del pool e i metodi di connessione per determinare dove potrebbero essere registrati e invocati i middleware pre- e post-query. Confronta i casi d’uso della conversione di asyncpgsa e delle metriche, quindi definisci l’API, l’ambito, l’ordine, il comportamento async e i test necessari prima dell’implementazione.

Scritto dal modello di indicizzazione a partire dal testo della issue.