Postgrest errors do not get caught, returns false positives

[rphly]

Bug report

Describe the bug

Example error that gets returned in 'data' instead of in 'error' in response from an .insert operation

{'data': {'hint': None, 'details': 'Failing row contains (null, 4, open-chat, 2021-07-12 16:04:41.982201+00).', 'code': '23502', 'message': 'null value in column "id" violates not-null constraint'}, 'status_code': 400}

To Reproduce

You can easily reproduce this with most errors like not-null constraints, missing columns.

In this case, all I did was try to insert a row with a null value in a not-null column

Expected behavior

error is not None

[J0]

Hey @rphly,

Thanks for reporting the bug! Just writing to let you know that I've seen the issue -- will look into it :)

[dreinon]

Hey @J0, have you been able to work on this at all?
If I get a bit of time this would be an issue I could handle 🙂

[dreinon]

Hi! This has been solved in the new version of postgrest-py! Now an APIError gets raised in this case.

Thanks for the report! Closing this issue now, but feel free to reopen it or comment here again if you have any other concerns 🙂