Opened 4 years ago
Last modified 4 years ago
#32092 closed New feature
Add an async db backend: asyncpg — at Version 1
| Reported by: | Andrew Chen Wang | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | database |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
This ticket wishes to add an asynchronous DB backend, namely using asyncpg.
I don't have much experience with the ORM itself, but I'd like to get the work started. One of the reasons this hasn't been started grandly is mentioned in DEP 9:
A lot of this stems from the fact that the underlying database drivers are synchronous
One thing that must take place before this ticket starts any code is the design decision. Don't know how to cc people, but I'd like to know what the design decision would be? Unlike cache.get_asyncwith that _async suffix, I feel like BaseDatabaseWrapper should just be duplicated into an AsyncBaseDatabaseWrapper? It wouldn't be DRY, so I'd love to know some thoughts!
Note:
See TracTickets
for help on using tickets.