hi, I am still having some issues with the interactive transactions API. for some reason it says this

Argument of type '() => Promise<Integration[]>' is not assignable to parameter of type 'PrismaPromise<any>[]'

const [updatedIntegration] = await this.prisma.$transaction(async () => {
    const method = ...

	const updatedIntegration = await this.prisma.integration.update({
		data: {
			name,
			username,
			password: hashedPassword,
			descriptionCharacterLimit,
			integrationMethodId: method.id
		},
		where: {
			id: integration.id
		}
	});

	// some more queries...

	return [updatedIntegration];
});

Hi! transactions expect you to pass a Promise. But you are passing the result of a Promise inside a custom Promise.

@Victor Iris

const updatedIntegration = await this.prisma.$transaction(async () => {
    const method = ...

	const updatedIntegration = this.prisma.integration.update({
		data: {
			name,
			username,
			password: hashedPassword,
			descriptionCharacterLimit,
			integrationMethodId: method.id
		},
		where: {
			id: integration.id
		}
	});

	// some more queries...

	return updatedIntegration;
});

like this?

let items = []

for (const integration of integrations) { const newPromise = this.prisma.integration.update({ data: { name, username, password: hashedPassword, descriptionCharacterLimit, integrationMethodId: method.id }, where: { id: integration.id } }); items.push(newPromise) } const itemsResults = await this.prisma.$transaction(items)

yes, I think so, let me try something

OOOOH, thanks for pointing that out @Dev__. Thats called interactive transactions. Thats a preview feature, do you have it on your schema.prisma client?

yes, I do

previewFeatures = ["orderByRelation", "referentialActions", "interactiveTransactions"]

seeing the same error from my side @Dev__. Would you mind opening an issue on Github?

yeah sure, i'll do it later today

@Dev__ 👋 Works fine for me:

yeah, I put a comment in the github issue

Hello @Ryan,

async function main() {
  const [user] = await prisma.$transaction(async () => {
    // Should the prisma object here need to the argument from this transaction or it can be the global prisma object initialized during application start?
    const user = await prisma.user.create({ data: { name: 'name' }})
    return [user]
  })

  prettyPrint(user)
}

Argument from the transaction only.

Ok

Yes, it doesn’t run in parallel.

But for the following example, it is returning false. but it should return true

const clearUser = async () => {
  return prisma.$transaction(async (p) => {
    const user = p.user.update({ where: { id: 1 }, data: { deleted: true }})
    const findUser = await p.user.fineOne({ where: { id: 1 }})
    return findUser.deleted
  })
}

const user =  await clearUser() // should return true, but in actual it is returning false.

You need to add

await

before the p.user.update call.

Oh sorry. In my real example, it is present. But i found the problem. I had queries inside the functions that are using global prismaclient, instead of the transaction prisma client. that may be the cause of issue. what do you say?