# DEP0009/ORM implementation plan

**URL:** https://forum.djangoproject.com/t/dep0009-orm-implementation-plan/33194
**Category:** Async
**Created:** [July 22, 2024, 2:52pm UTC](https://forum.djangoproject.com/t/dep0009-orm-implementation-plan/33194 "2024-07-22T14:52:30Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![fcurella](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/fcurella/32/70_2.png) [@fcurella](https://forum.djangoproject.com/u/fcurella)
#### Post date: [November 25, 2024, 4:35pm UTC](https://forum.djangoproject.com/t/dep0009-orm-implementation-plan/33194/10 "2024-11-25T16:35:35Z")

</div>

> - if we are not within a `new_connection` context, `aget` just falls back to `get`. In other words, existing behavior is maintained unless you opt into the new API.

This is the behavior [I previously proposed](https://forum.djangoproject.com/t/dep0009-orm-and-backward-compatibility/32175/6), and it seemed well received.

> Make sync connections just wrap an async connection. Psycopg’s `AsyncConnection` is thread-safe,

This option is interesting, but I don’t know if we can count and async connections being portable for every backend. Would this work on, let’s say, async SQLite?

---

_[View the full topic](https://forum.djangoproject.com/t/dep0009-orm-implementation-plan/33194)._