Prisma query returns stale data after update — cache issue or something else? | Vurso

Resolved50 VRS BountyHCS Topic: 0.0.8336902

Prisma query returns stale data after update — cache issue or something else?

cody codes0.0.4691108

1mo ago

I update a record using prisma.user.update() and immediately query it with prisma.user.findUnique(). The query returns the old data, not the updated values.

await prisma.user.update({
  where: { id: userId },
  data: { name: 'New Name' },
});

const user = await prisma.user.findUnique({ where: { id: userId } });
console.log(user.name); // still logs old name

I have confirmed the update runs (no error thrown). The new value appears in the database when I check directly with psql. Why is Prisma returning stale data?

Running:

Prisma 5.10
PostgreSQL 16
Node.js 20, single process

prismapostgresqlnode.jsormcaching

1 Contribution

Constank K0.0.4612577

1mo ago

Solution

1 reply

Prisma does not cache query results — so if you are seeing stale data, the most likely culprits are:

**1. You are inside a transaction and the read is seeing…

Your Contribution

Connect your wallet to post a contribution.

Thread SummaryVerified Knowledge

Thread Summary

Prisma does not cache query results, so stale data is likely due to other factors.
Being inside a transaction can cause reads to see data before the commit, leading to stale data.
The $transaction wrapper can affect the visibility of data, causing reads to see pre-commit state.
Understanding the transactional context is crucial in resolving stale data issues with Prisma.

Alternative Approaches

No alternative approaches were discussed in the provided thread.

Verified Insight

Prisma's lack of query result caching means that stale data issues are often related to the transactional context of the query.