Revalidate prisma query in `page.ts` RSC

I'm getting the same data every time I visit this route.

import { prisma } from "@acme/db";
import EditForm from "./edit-form";

export default async function Page({ params }: { params: { id: string } }) {
  const account = await prisma.account.findUnique({
      where: {
        id: Number(params.id),
      }
  })

  if (!account) return "Account doesn't exist";

  return <EditForm account={account} />;
}

import { prisma } from "@acme/db";
import EditForm from "./edit-form";

export default async function Page({ params }: { params: { id: string } }) {
  const account = await prisma.account.findUnique({
      where: {
        id: Number(params.id),
      }
  })

  if (!account) return "Account doesn't exist";

  return <EditForm account={account} />;
}

import { prisma } from "@acme/db";
import EditForm from "./edit-form";

export default async function Page({ params }: { params: { id: string } }) {
  const account = await prisma.account.findUnique({
      where: {
        id: Number(params.id),
      }
  })

  if (!account) return "Account doesn't exist";

  return <EditForm account={account} />;
}

import { prisma } from "@acme/db";
import EditForm from "./edit-form";

export default async function Page({ params }: { params: { id: string } }) {
  const account = await prisma.account.findUnique({
      where: {
        id: Number(params.id),
      }
  })

  if (!account) return "Account doesn't exist";

  return <EditForm account={account} />;
}

Is there a way to revalidate prisma queries in a RSC?

Neto•5/8/23, 2:14 PM

try add

Neto•5/8/23, 2:14 PM

export const revalidate = 0;export const revalidate = 0;

Neto•5/8/23, 2:14 PM

the explanation for it

Neto•5/8/23, 2:14 PM

0: Ensure a layout or page is always dynamically rendered even if no dynamic functions or dynamic data fetches are discovered. This option changes the default of fetch requests that do not set a cache option to 'no-store' but leaves fetch requests that opt into 'force-cache' or use a positive revalidate as is.

pedro77OP•5/8/23, 2:17 PM

The problem is revalidaterevalidate and all the other functions like revalidatePathrevalidatePath and revalidateTagsrevalidateTags all seem to work only for the

fetch

fetch

implementation next team made, not for prisma

pedro77OP•5/8/23, 2:17 PM

@nyx (Rustular DevRel) Tried it anyway, nothing changes

pedro77OP•5/8/23, 2:19 PM

The only way I don't get staled data is by doing full page reload which, I mean, it definitely sucks... the whole point of RSC is not to make a backend, isn't it? I feel like I need a backend right now

n1xx1•5/8/23, 2:21 PM

does export const dynamic = "force-dynamic"export const dynamic = "force-dynamic" help?

pedro77OP•5/8/23, 2:22 PM

No @n1xx1

pedro77OP•5/8/23, 2:27 PM

So my question is: is it possible to revalidate anything other than fetch()fetch() functions?

pedro77OP•5/8/23, 2:28 PM

I asked in the Nextjs discord and nobody seems interested in answering that question

n1xx1•5/8/23, 2:28 PM

I mean, it's supposed to work like you expect. I'm not sure what's going on

Neto•5/8/23, 2:29 PM

it should be able

pedro77OP•5/8/23, 2:29 PM

I'll work on a code sandbox

Neto•5/8/23, 2:29 PM

next dedupe fetch requests

Neto•5/8/23, 2:29 PM

but i know that it will cache pages in general

n1xx1•5/8/23, 2:31 PM

also it's a page with params, it's dynamic by default, it's not supposed to cache anything. try to reproduce in the codesandbox, maybe it's helpful!

n1xx1•5/8/23, 2:31 PM

also make sure you're on next 13.4 I guess, I remember some issues with dev mode page caching

pedro77OP•5/8/23, 2:35 PM

I'm on it

pedro77OP•5/8/23, 4:15 PM

@nyx (Rustular DevRel) @n1xx1

https://codesandbox.io/p/sandbox/gifted-microservice-fphtss?file=%2Fapp%2Fadd%2Fadd-form.tsx

gifted-microservice-fphtss

CodeSandbox is an online editor tailored for web applications.

pedro77OP•5/8/23, 4:16 PM

Add and modify a post in that codesandbox please

pedro77OP•5/8/23, 4:17 PM

If you try to modify the second time, you'll get staled data

Neto•5/8/23, 4:19 PM

if i modify the code

Neto•5/8/23, 4:19 PM

it creates a new sandbox for me

Neto•5/8/23, 4:19 PM

// page.tsx

import AddForm from "./add-form";

export const revalidate = 0;

export default function Page() {
  return <AddForm />;
}

// page.tsx

import AddForm from "./add-form";

export const revalidate = 0;

export default function Page() {
  return <AddForm />;
}

Neto•5/8/23, 4:19 PM

add this on page.tsx

Neto•5/8/23, 4:21 PM

add that to the root page

Neto•5/8/23, 4:21 PM

on /app/page.tsx/app/page.tsx

pedro77OP•5/8/23, 4:22 PM

I added that and doesn't help bro

pedro77OP•5/8/23, 4:24 PM

Bro, I feel like a beta tester, app router is stable, isn't it? How is this not working?

Neto•5/8/23, 4:24 PM

is not stable

Neto•5/8/23, 4:24 PM

it never was

pedro77OP•5/8/23, 4:24 PM

The docs says is stable, they lie to us?

n1xx1•5/8/23, 4:25 PM

ok I see what's going on, the data is changing but react-hook-form won't update your default variables

pedro77OP•5/8/23, 4:26 PM

Why not? it's unmounted everytime we use it

pedro77OP•5/8/23, 4:27 PM

react-hook-form can't persist data, as far as I can see

Neto•5/8/23, 4:29 PM

// add-form.tsx
router.refresh();
router.push("/");

// add-form.tsx
router.refresh();
router.push("/");

Neto•5/8/23, 4:29 PM

will purge the page

Neto•5/8/23, 4:30 PM

and refresh accordingly

pedro77OP•5/8/23, 4:33 PM

Yeah, that might work (workaround), just I was expecting revalidatePath()revalidatePath() to do what the name of the function suggests

pedro77OP•5/8/23, 4:36 PM

It's kinda disheartening to feel like nobody has thought of this simple issue, are these features getting adopted or is it just me?

pedro77OP•5/8/23, 4:37 PM

moment of sadness theoDisgusted

n1xx1•5/8/23, 4:50 PM

I guess I never tried without doing a full refresh B)

pedro77OP•5/9/23, 3:03 PM

Next team is working on this issue:

https://github.com/vercel/next.js/issues/49496#issuecomment-1540135469

GitHub

Revalidate anything other than `fetch()` · Issue #49496 · vercel/ne...

Verify canary release I verified that the issue exists in the latest Next.js canary release Provide environment information Operating System: Platform: linux Arch: x64 Version: #22 SMP Tue Jan 10 1...

Revalidate prisma query in `page.ts` RSC

Similar Threads

Similar Threads

Similar Threads