Hi @MichaelNZ85, this should already be possible via Prisma's $extends() (link to the docs).

The idea is that you can create wrappers for certain operations within Prisma itself, so you can add your own custom logic before or after Prisma executes that query.

You can add logs, modify Prisma filters, invoke async operations tied to your own business logic, and so on.

Please give it a try and let us know whether this information is enough to close this issue :)
Thanks!

Hi @MichaelNZ85, this should already be possible via Prisma's $extends() (link to the docs).

The idea is that you can create wrappers for certain operations within Prisma itself, so you can add your own custom logic before or after Prisma executes that query.

You can add logs, modify Prisma filters, invoke async operations tied to your own business logic, and so on.

Please give it a try and let us know whether this information is enough to close this issue :) Thanks!

I gave it a try and found that it is not possible to create @AfterInsert event listener. In all docs you can see examples of executing something before query(args). I tried to overcome this by doing the following (simplified version, not real thing):

export async function onUserCreated(user_id: string, args: Prisma.userCreateArgs) {
   const newUser = await prisma.user.findFirstOrThrow({
        where: {
            user_id: user_id
        }
    });
   await calculateUserStatus(newUser); //some complex logic there
}

const prisma = new PrismaClient().$extends({
  query: {
    user: {
      async create({ model, operation, args, query }) {
        const result = await query(args);
        await onUserCreated(result.user_id, args); //this function will succeed 
                                                  //only if the record has been saved into DB 
                                                  //and the transaction has been committed
        return result;
      },
    },
  },
})

Then I tried the following:

const prisma = new PrismaClient().$extends({
  query: {
    user: {
      async create({ model, operation, args, query }) {
        let create_result: any;
        return query(args)
                 .then((result) => {
                       create_result = result1;
                       return onUserCreated(result.user_id, args)
                          .then(() => {
                              return create_result;
                            }) 
                });
      },
    },
  },
})

Both variants failed to find the user we just created in the DB and the calculation on it is impossible.

Although I found that prisma does not commit the transaction until the extended create function returns the result. Therefore, $extends() can't be used to create listeners that should be executed only after the record has been created in the database. We have to, as you said, "invoke async operations tied to your own business logic" in separate thread based on hope that the final transaction commit in the extended method will be completed successfully. We need more concrete guarantees of the fact that the record has been indeed created in the DB so we can execute additional logic that is dependent on presence of the new record there.

Please let us know if there is a solution for @AfterCreate listeners in Prisma API.