Open flea89 opened 2 years ago
At the moment it is pretty difficult to discriminate between different DBError messages.
Within our DBClient if an error occurs we generally raise a DBError.
DBError
DBError has always code 'ERROR_DB and it doesn't store the actual DBError so it's impossible for client code to catch different types of error.
'ERROR_DB
We should make sure the Postgrest code is store in the error or even better, create different errors based on that code.
Possible solutions:
Removing this from the PSA Epic and adding as a separate item to the backlog.
Discussed with @alanshaw . Probably needs to be looked at, but low priority for the moment.
At the moment it is pretty difficult to discriminate between different DBError messages.
Within our DBClient if an error occurs we generally raise a
DBError
.DBError
has always code'ERROR_DB
and it doesn't store the actual DBError so it's impossible for client code to catch different types of error.We should make sure the Postgrest code is store in the error or even better, create different errors based on that code.