using connect in interactive transaction fails

[steliosrammos]

Bug description

Hey, I am trying to run an interactive transaction which has the following sequence:

1. creates a wallet
2. creates a wallet link using the wallet's id with a connect statement

The transaction fails with the following error:

An operation failed because it depends on one or more records that were required but not found. No 'Wallet' record(s) (needed to inline the relation on 'WalletLink' record(s)) was found for a nested connect on one-to-many relation 'wallet_linkerTowallet'.

How to reproduce

Here's what the transaction looks like:

  const result = await models.$transaction(async (prisma) => {
      const tempConnectionDetails = await prisma.lndConnectionDetails.create({
        data: {
          hostname,
          grpcPort,
          tlsCertificate: lndNodeType === voltage ? undefined : (tlsCertificate || undefined),
          macaroon: base64macaroon,
          lndNodeType: lndNodeType as LndNodeType,
        },
      });

      const tempWallet = await prisma.wallet.create({
        data: {
          name: name || hostname,
          connectionDetailsType: lnd,
          connectionDetailsId: tempConnectionDetails.id,
          users: {
            create: [{ role: WalletOwner, user: { connect: { id: this.apolloContext.user!.id } } }],
          },
        },
      });

      const walletLink = models.walletLink.create({
        data: {
          wallet: { connect: { id: tempWallet.id } },
          resourceId,
          resourceType: resourceType as WalletResourceType,
        },
      });
      return walletLink;
    });

Note that when printing the tempWallet var in the transaction, it does show the record with an id.

Expected behavior

No response

Prisma information

Relevant part of the schema:

model WalletLink {
  id           BigInt             @id @default(autoincrement())
  resourceId   BigInt             @map("resource_id")
  resourceType WalletResourceType @map("resource_type")
  walletId     BigInt             @map("wallet_id")

  wallet Wallet @relation("wallet_linkTowallet", fields: [walletId], references: [id])

  @@unique([walletId, resourceId, resourceType], name: "uniqueWalletLink")
  @@index([resourceId, resourceType], map: "wallet_link.resource_index")
  @@map("wallet_link")
}

model Wallet {
  id                    BigInt                @id @default(autoincrement())
  name                  String
  connectionDetailsId   BigInt                @map("wallet_id")
  connectionDetailsType ConnectionDetailsType @map("wallet_type")

  users WalletUser[] @relation("wallet_userTowallet")
  links WalletLink[] @relation("wallet_linkTowallet")

  @@map("wallet")
}

Environment & setup

• OS: Mac OS
• Database: PostgreSQL
• Node.js version: v16.16.0

Prisma Version

prisma                  : 3.15.2
@prisma/client          : 3.15.2
Current platform        : darwin
Query Engine (Node-API) : libquery-engine 461d6a05159055555eb7dfb337c9fb271cbd4d7e (at node_modules/@prisma/engines/libquery_engine-darwin.dylib.node)
Migration Engine        : migration-engine-cli 461d6a05159055555eb7dfb337c9fb271cbd4d7e (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core 461d6a05159055555eb7dfb337c9fb271cbd4d7e (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt 461d6a05159055555eb7dfb337c9fb271cbd4d7e (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash    : 461d6a05159055555eb7dfb337c9fb271cbd4d7e
Studio                  : 0.462.0
Preview Features        : interactiveTransactions

[annibuliful]

I think you should change

const walletLink =await prisma.walletLink.create({
        data: {
          wallet: { connect: { id: tempWallet.id } },
          resourceId,
          resourceType: resourceType as WalletResourceType,
        },
      });

because when you run transaction it if you need primary key or some data from another INSERT/UPDATE from another model in the same transaction, you must use the same transaction id to get them

[garrensmith]

@steliosrammos could you try what @annibuliful has suggested. You need to make sure that all operations are using the transaction client and not the main prisma client.

[danstarns]

Added a test for this here: #15640

@steliosrammos

It looks like you are not using the transaction instance inside your transaction for the call walletLink.create. I suggest you use the prisma transaction instance passed into the callback:

- const walletLink = models.walletLink.create({
+ const walletLink = prisma.walletLink.create({
    data: {
      wallet: { connect: { id: tempWallet.id } },
      resourceId,
      resourceType: resourceType as WalletResourceType,
    },
  })
  return walletLink

The tests I have added assert that we can use the connect nested operation inside a transaction, so please could you try again using my suggestion and also with the latest version of Prisma?