uri Posts - Answer Overflow

uri

•Created by uri on 3/6/2025 in #help

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?

6 replies

DTDrizzle Team

•Created by uri on 3/4/2025 in #help

How should I refactor my transactions?

Hi, I wondering how I should refactor my code. Right now I have forms in which data affects multiple tables and its relations and I use a transaction to make sure data consistency when adding or updating. I'd like to split the transaction into different functions and even different files. I was thinking I could simply send my transaction object to the function but I don't like this approach since the query function then is dependent on receiving the transaction object. In case I don't need the query to be in a transaction I could send the transaction object (tx) as optional and then check and execute tx.query or db.query, but I don't like this approach. So I am asking, is there a more elegant solution to split my transaction queries into different files and functions? Thank you!

3 replies

DTDrizzle Team

•Created by uri on 2/13/2025 in #help

Best practices for inferring types in queries?

I'm refactoring my app and I'm trying to keep my schema as the single source for my data types, at least for my model data. Inferring types has worked wonders for inserting and making basic queries. However, for more complex queries with nested data I've tried to make intersection types matching the structure of the query result, but ts doesn't like that (the structure might not be identical), and explicit casting doesn't seem to work either. For instance, having something like this:

 const users= await db.query.user.findMany({
        with: {
            posts: {
                with: {
                    post: true,
                },
                columns: {
                    userId: false,
                    postId: false,
                },
            },
            postGroup: true,
            images: true,
        },
    });

 const users= await db.query.user.findMany({
        with: {
            posts: {
                with: {
                    post: true,
                },
                columns: {
                    userId: false,
                    postId: false,
                },
            },
            postGroup: true,
            images: true,
        },
    });

I tried to create the type (didn't work):

export type User = BaseUser & {
    posts: Post[],
    postGroup: PostGroup
    images: Images[],
}

export type User = BaseUser & {
    posts: Post[],
    postGroup: PostGroup
    images: Images[],
}

Another idea I have is that I could infer the type from the users object, but in that case that would imply having my user queries centralized in some place so I could export their types to the multiple places needed. I'm trying to find a way to get proper typing while avoiding to duplicates or having to manually write types them throughout my app. What do you think it could be an elegant solution? Thank you!

1 replies

Gaming

Programming