Best practises for handling postresql errors?
Hi, I was wondering which is the recommended way to handle postresql errors in drizzle.
Until now I was making sure all introduced data wasn't triggering any error, so for example when I introduce a new Item I manually check if there is already another item with the same name. However I was thinking whether might be a good idea to let postgresql throw an error and just catch it in my drizzle query.
One option I've seen is this https://github.com/drizzle-team/drizzle-orm/discussions/916#discussioncomment-11929987
So I have 2 questions
1) is this a good practise? or is it better to manually manage errors instead of letting postresql complain? The former could be easier if there was any way to handle those errors and
2) in case this is a good enough practise, is there any way drizzle can manage and identify those errors so I can return a proper error message to the frontend?
Until now I was making sure all introduced data wasn't triggering any error, so for example when I introduce a new Item I manually check if there is already another item with the same name. However I was thinking whether might be a good idea to let postgresql throw an error and just catch it in my drizzle query.
One option I've seen is this https://github.com/drizzle-team/drizzle-orm/discussions/916#discussioncomment-11929987
So I have 2 questions
1) is this a good practise? or is it better to manually manage errors instead of letting postresql complain? The former could be easier if there was any way to handle those errors and
2) in case this is a good enough practise, is there any way drizzle can manage and identify those errors so I can return a proper error message to the frontend?
