Added none query feature:

in Django ORM, calling none() will create a queryset that never returns any objects and no query will be executed when accessing the results. A qs.none() queryset is an instance of EmptyQuerySet.

example:

Entry.objects.none() <QuerySet []> from django.db.models.query import EmptyQuerySet isinstance(Entry.objects.none(), EmptyQuerySet) True

I have no idea if this will work, but maybe it will?

Here's a bit of my research on what I was thinking: https://github.com/rednaks/django-async-orm/discussions/9

web_1         | DEBUG:root:concurrent.futures.Future is expected, got <gevent.threadpool._FutureProxy object at 0x7fcabce2e9d0>
web_1         | DEBUG:root:concurrent.futures.Future is expected, got <gevent.threadpool._FutureProxy object at 0x7fcabf109bb0>
web_1         | DEBUG:root:concurrent.futures.Future is expected, got <gevent.threadpool._FutureProxy object at 0x7fcabf109250>
web_1         | DEBUG:root:concurrent.futures.Future is expected, got <gevent.threadpool._FutureProxy object at 0x7fcabc5654f0>
web_1         | DEBUG:root:concurrent.futures.Future is expected, got <gevent.threadpool._FutureProxy object at 0x7fcabd7846d0>
^CGracefully stopping... (press Ctrl+C again to force)
Stopping benchmark-django-fastapi_web_1      ... done
Stopping benchmark-django-fastapi_postgres_1 ... done

looks kind of close ... although something is expecting concurrent.futures.Future instead of also allowing gevent.threadpool._FutureProxy

update

a recursion error of some sort logged from here : https://github.com/rednaks/django-async-orm/pull/7/files#diff-142ac986547c5b13f77ae025cb60609eed65082cc41ac6e81f4b778422d50017R116

recursion.error.txt

Thanks for sharing this library. Very interesting!

Any suggestions on why NoneType would be returned from async_all?

web              |   File "/venv/lib/python3.8/site-packages/fastapi/applications.py", line 199, in __call__
web              |     await super().__call__(scope, receive, send)
web              |   File "/venv/lib/python3.8/site-packages/starlette/applications.py", line 112, in __call__
web              |     await self.middleware_stack(scope, receive, send)
web              |   File "/venv/lib/python3.8/site-packages/starlette/middleware/errors.py", line 181, in __call__
web              |     raise exc from None
web              |   File "/venv/lib/python3.8/site-packages/starlette/middleware/errors.py", line 181, in __call__
web              |     raise exc from None
web              |   File "/venv/lib/python3.8/site-packages/starlette/exceptions.py", line 93, in __call__
web              |     await response(scope, receive, sender)
web              |   File "/venv/lib/python3.8/site-packages/starlette/exceptions.py", line 93, in __call__
web              |     await response(scope, receive, sender)
web              |   File "/venv/lib/python3.8/site-packages/starlette/routing.py", line 580, in __call__
web              |     await route.handle(scope, receive, send)
web              |   File "/venv/lib/python3.8/site-packages/starlette/routing.py", line 241, in handle
web              |     await self.app(scope, receive, send)
web              |   File "/venv/lib/python3.8/site-packages/starlette/routing.py", line 52, in app
web              |     response = await func(request)
web              |   File "/venv/lib/python3.8/site-packages/fastapi/routing.py", line 201, in app
web              |     raw_response = await run_endpoint_function(
web              |   File "/venv/lib/python3.8/site-packages/fastapi/routing.py", line 148, in run_endpoint_function
web              |     return await dependant.call(**values)
web              |   File "/app/api/generated_app/main.py", line 100, in get_buildings
web              |     data = await get_data()
web              |   File "/app/api/generated_app/main.py", line 88, in get_data
web              |     async for building in data:
web              |   File "/venv/lib/python3.8/site-packages/django_async_orm/query.py", line 71, in __aiter__
web              |     return AsyncIter(self._result_cache)
web              |   File "/venv/lib/python3.8/site-packages/django_async_orm/iter.py", line 6, in __init__
web              |     self._iter = iter(iterable)
web              | TypeError: 'NoneType' object is not iterable

py3.8.10 django3.2

async def get_data():
    data = await Building.objects.async_all()
    result = []
    async for building in data:
        print(data, dir(data))
        print(building.__dict__)
        result.append({"id": building.id, "number": building.number})
    return result

@app.get("/buildings", response_model=List[BuildingSummary])
async def get_buildings(limit: conint(le=500), skip: conint(le=500)) -> List[BuildingSummary]:
    """
    Building List
    """
    # this is a custom thing
    data = await get_data()
    return data

async def get_data():
    return await Building.objects.async_all()

@app.get("/buildings", response_model=List[BuildingSummary])
async def get_buildings(
    limit: conint(le=500),
    skip: conint(le=500),
    x_pm_org: Optional[List[int]] = Header(None, alias="x-pm-org"),
    x_pm_org_id: Optional[List[int]] = Header(None, alias="x-pm-org-id"),
    x_pm_user_type: Optional[str] = Header(None, alias="x-pm-user-type"),
) -> List[BuildingSummary]:
    """
    Building List
    [{'ApiKeyAuth': []}, {'PmOrg': []}]
    """

    org.set(x_pm_org)
    pydant, item_all = paths["get_buildings"]



    # this works
    data = await get_data()

    # this also works
    data2 = await Buildings.objects.async_all()



    result = []
    async for item in data[skip:limit]:
        print(item.__dict__)
        result.append(pydant.from_orm(item).dict())
    return result

Related to: #2

I just tested it locally and it appears to work.

Thanks for the quick response.

Not sure where to ask this, possibly could enable the "discussions" section on the repo?

But how does the ThreadPoolExecutor work with something like psycogreen/eventlet?

when we patch models, we prefix the methods with async_ but the new official django api prefixes the methods with a ex:

patched api : sync objects.get => async objects.async_get official api: sync objects.get => async objects.aget

so to make it forward compatible we need to comply to django's new api.

be aware to keep our api so we don't break the internet

Hello! After installing django_async_orm facing such problem with default update_or_create() function

Do you have any ideas by a chance why is it going like this?

python 3.8 django 3.2.9 django-async-orm latest

Hi, @rednaks,

I have added the count feature and test for the same, and with that, I have also changed some other tests accordingly and removed unused imports from the file. Please have a look and give your feedback.

Perhaps it's worth starting django-channels library for asynchronous db calls?

There is a function there. And, as I understand it, it will be more effective than it is now.