Async support

[shaib]

Apparently, at least as of Django 5.2, most async ORM methods are implemented as sync_to_async() wrappers around the synchronic methods. This means we get async support by default.

But we probably do need to take a pass over the new ORM methods and see if there's anything we need to add.

[golanBar]

We should choose between synchronous and asynchronous queries based on the specific task. A hybrid approach that uses both is the most effective.

[yonijacobi]

@shaib Looks like an async version for refresh_from_db should be created because it uses additional argument which is not in the django's built in method (all_parents)
def refresh_from_db(self, using=None, fields=None, from_queryset=None, *, all_parents: bool = False)
I think this is the only case of its kind.
And maybe also async version of delete is needed because it uses the synced refresh_from_db in it

[shaib]

Looks like an async version for refresh_from_db should be created because it uses additional argument which is not in the django's built in method (all_parents)

Makes sense

I think this is the only case of its kind. And maybe also async version of delete is needed because it uses the synced refresh_from_db in it

Correct (and yes, adelete() on the model is needed). It should be noted that -- by happy circumstance, not planning -- the methods which extend the API (BrokenDownQuerySet: fetch_all_parents(), update_fetched_parents(), select_related_with_all_parents(); BrokenDownModel: getattr_if_loaded()) do not need async versions, because they all work in-memory and do not access the database.