Drizzle Team•5w ago

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?

3 Replies

David L. Bowman•5w ago

i was literally about to ask this same question. i'm currently using

        const task = Effect.tryPromise({
            try: () =>
                db
                    .select({ role: users.role })
                    .from(users)
                    .where(eq(users.emailHash, emailHash)),
            catch: (error) => new UnexpectedError({ reason: error }),
        });

        const task = Effect.tryPromise({
            try: () =>
                db
                    .select({ role: users.role })
                    .from(users)
                    .where(eq(users.emailHash, emailHash)),
            catch: (error) => new UnexpectedError({ reason: error }),
        });

id be interested in hearing what other people do.

AlexDaniel•4w ago

when I introduce a new Item I manually check if there is already another item with the same name

And how do you avoid race conditions? See also: https://orm.drizzle.team/docs/insert#upserts-and-conflicts

uriOP•4w ago

Race conditions are always tricky. In my case there will be very few concurrent users modifying this data, the data is not critical, and I check and the update in the same transaction. Despite all this I appreciate any other insight on this issue. It would be nice if I could execute a method in .onConflict , I don't want to do anything in the database when a conflict occurs, I just want to warn the user. So my doubts are whether is better lo let postgresql complain and catch the error, make all checking by myself as I'm already doing, or exploring if there exists a better way with drizzle to handle conflicts and warn the frontend user.

Gaming

Programming

Best practises for handling postresql errors?

Did you find this page helpful?