How to handle Postgres errors inside try catch (with Drizzle)?

[juanvilladev]

I'm trying to understand how to properly type my errors when Drizzle throws due to a Postgres error.

Example, when I attempt to insert a number into a string column, I was thinking within my catch block I could use:

   try {
      const savedPurchaseOrder = await tx
        .insert(purchaseOrderReadModel)
        .values(purchaseOrderCreatedPayload)
        .returning({
          id: purchaseOrderReadModel.id,
        });

      if (!savedPurchaseOrder[0]) {
        tx.rollback();
      }
      purchaseOrderId = savedPurchaseOrder[0].id;
    } catch (e) {
      if (e instanceof TransactionRollbackError) {
        //Here is the logic for my manual rollback which is executed whenever we hit tx.rollback()
      }
      if (e instanceof DrizzleError) {
        //Here is where I expected I'd get the error, however it looks like e is not an instanceof DrizzleError
      }

      tx.rollback();
    }

Should I just use PostgresError?

Thanks!

[d3vr10]

Does anyone know ? I'm stumbling upon the same situation right now.

[FlaTrix1]

I noticed that the error message comes from the database library I use in drizzle. In my case, it is "pg".
import { DatabaseError } from 'pg';, and then err instanceof DatabaseError works.

[shawnmclean]

Is this concept possible in the first place?

I'm running a try catch inside a transaction to watch for a db conflict error, but the entire transaction is throwing this error while the closure in the transaction keeps on running.

For example:

  await db.transaction(async (tx) => {
    let retryCount = 0;
    while (retryCount < 10) {
      try {
       await tx.insert()

      } catch (error) {
        const queryError = error as QueryError;
        if (
          typeof queryError.code === "string" &&
          queryError.code === "23505"
        ) {
          // Unique violation (Postgres specific error code)
          // Regenerate slug by appending a unique identifier (e.g., retryCount)
          slug = slugify(knowledge.title) + "-" + (retryCount + 1);
          retryCount++;
        } else {
          throw error; // Re-throw other errors
        }
      }
    }
}

But once the first error is thrown, the entire transaction seems to return, while the code just continues to execute.