Content
@
0 reply
0 recast
0 reaction
pugson
@pugson
the inevitable curse of next.js + ORM cache is kicking my ass today. had to spend a few hours optimizing queries and rewriting to a client component to figure out some live piece of data π΅βπ«
3 replies
0 recast
36 reactions
pugson
@pugson
update: i am now back to a full server component and everything works perfectly lol
0 reply
0 recast
17 reactions
dylan
@dylsteck.eth
they really need to change their caching defaults lol
2 replies
0 recast
6 reactions
Joe Blau π©
@joeblau
Heh! Iβve run into this a lotβ¦ I had to throw 0 second cache limits everywhere to get next to give me live data. I probably should have just used web sockets.
0 reply
0 recast
2 reactions
