ItemsService in extensions fails on table with BigInt primary key about directus HOT 7 CLOSED

The error itself doesnt look to be related to a big int key but rather service.readByQuery() is missing the required first query parameter. Try adding an empty object if you're not querying anything specific:

await testService.readByQuery({});

closing this issue for now but happy to re-open if im incorrect 😄

from directus.

The error itself doesnt look to be related to a big int key but rather service.readByQuery() is missing the required first query parameter. Try adding an empty object if you're not querying anything specific:

await testService.readByQuery({});

closing this issue for now but happy to re-open if im incorrect 😄

My bad, I forgot to add the empty object.
But it's still not working even with an empty object

from directus.

Are you getting a different error then i'd expect?

from directus.

Nope, the exact same error as above

from directus.

Alright, my bad again I had a typo in my table name.
However, I find it weird that I still have the issue with the new table "test" I created

from directus.

Could that perhaps be cache? on second look the error would indicate that the collection you're using is not in the provided schema as it tries to do schema[collection].fields (which would throw the accessing fields of undefined error)

from directus.

Totally, just ran some tests it is indeed related to cache ;)

from directus.