like have similar caching such as fetch?

its just a postgres db, so you can fetch anything as long as it exists on the db. Give further information what you mean by tags etc

tags as in https://nextjs.org/docs/app/building-your-application/caching#fetch-optionsnexttags-and-revalidatetag

yeah then ^ is basicly the only way for custom fetch implmentations

but it's unstable :(, what's the best alternative to invalidate the cache? router.refresh()?

that would invalidate client cache

depending on how you use your neondb, you may be able to cache the pages and just revalidate them

with revalidatePath?

with revalidateTag

you dont need to actually store the tag anywhere

it can be hard coded

yeah, you would use this to revalidate pages

and then use router.refresh to make sure the user has it updated

not sure about this ^

i don't believe so

can you explain this please?

i just wanted to put the docs here: https://nextjs.org/docs/app/building-your-application/caching#fetch-optionsnexttags-and-revalidatetag

revalidatePath vs. router.refresh:
- Calling router.refresh will clear the Router cache, and re-render route segments on the server without invalidating the Data Cache or the Full Route Cache.
- The difference is that revalidatePath purges the Data Cache and Full Route Cache, whereas router.refresh() does not change the Data Cache and Full Route Cache, as it is a client-side API.

im not sure what he is getting at here tbh

meaning you dont need to fetching the tags from anywhere. you can literally hard-code the tag in the fetch request

cause u initially said something about tags

i guess i just got confused

yeah, that's what i wanted to do as well but i'm not sure how to do this with neon :D hence my question

how are you fetching your data with neon?

i wanted to pass a custom fetch function to their basic config but it looks like it doesn't accept any arguments

even if they use the right fetch, you would have to make an insane wrapper to add the tags

Technically they provide a databaseurl to you, so you should just be able to use a ORM or something

still the same cache issue

import { schema } from "...";
import { Pool, neonConfig } from "@neondatabase/serverless";
import { drizzle } from "drizzle-orm/neon-serverless";
import { env } from "@/env.mjs";

neonConfig.fetchConnectionCache = true;

const pool = new Pool({ connectionString: env.DB_URL });

export const db = drizzle(pool, {
  schema,
  logger: env.NODE_ENV !== "production",
});

db.query.someEntry.findMany(...)

yeah without using unstable_cache, i don't see how you would use nextjs cache

but using unstable_cache is better than any sketchy implementation of abusing fetch....

for a production app? you'd think it's better than using revalidatePath + cache + router.refresh as a temporary solution?

its up to you tbh

i would say they are both good implmentations

but you will still need .refresh if the user wants update

and is the "cache" the route cache (not any other one)?

by cache i meant https://nextjs.org/docs/app/building-your-application/caching#react-cache-function

ahh that cache is only useful for the same request

like if you use the same function twice in a render (only done once)

but it doesn't affect cross requests

ohhh okay, okay, looks like i misunderstood its functionality

thank you for the advice and for clearing this up :D

yeah otherwise unstable_cache is useless

so your question is answered?

yup :D thank you