Please provide more info on return types from execute

[songololo]

The return types from execute currently require trial and error to unpack. Would it be possible to add more information in the README.md explaining what the potential return types are and what they mean?

e.g. the returned value seems to have changed from a prior version of postgrest-py: it now returns a tuple of data and a None value. But it isn't clear what this None value represents and how to handle potential response errors on the return types?

[dreinon]

Hi! Thanks for reporting. We have an open PR to solve this, which only needs a few tests to be written

[dreinon]

Btw, that None value is intended to be the count value if you ask for it in the query.

[dannmate]

I am finding the return types are different also from selecting data, to inserting/updating, looking forward to the PR :)

[dreinon]

Hi! This issue should be solved with the new version of postgrest-py and supabase-py, we use a pydantic model now to represent a Response, which has two properties, data and count, and you'll get an APIError raised if the call returns an error 🙂.

Closing this issue, but feel free to reopen or comment here if you have any more concerns, thanks!

[Filsommer]

In which supabase version was this implemented? I still get type Any pretty much everywhere when executing supabase queries in python. Using supabase==1.0.3