App ainda lendo dados antigos após migração para Neon DB via Prisma
Hi Neon team 
I'm using Neon PostgreSQL with my Node.js + Prisma app (Autônoma.app).
After migrating from a local JSON database to Neon via Prisma, the app seems to still “read phantom data” from old builds when deployed through Railway.
Environment:
- Railway connected to GitHub (production)
- Neon DB active (Postgres)
- Prisma fully integrated
- Old JSON file removed
- Cache disabled in Express middleware (res.set('Cache-Control', 'no-store'))
I’d like to confirm:
1. How to fully clear any cached or phantom data from Neon / Railway builds.
2. If I can check active connections or branches on Neon to ensure it's reading only the Neon DB.
3. If backups are enabled automatically for my current plan.
Project: Autônoma.app
Database: [coloque aqui o link do seu banco Neon]
Environment: Production
Thanks in advance
— Kadu Costa
I'm using Neon PostgreSQL with my Node.js + Prisma app (Autônoma.app).
After migrating from a local JSON database to Neon via Prisma, the app seems to still “read phantom data” from old builds when deployed through Railway.
Environment:- Railway connected to GitHub (production)
- Neon DB active (Postgres)
- Prisma fully integrated
- Old JSON file removed
- Cache disabled in Express middleware (res.set('Cache-Control', 'no-store'))
I’d like to confirm:1. How to fully clear any cached or phantom data from Neon / Railway builds.
2. If I can check active connections or branches on Neon to ensure it's reading only the Neon DB.
3. If backups are enabled automatically for my current plan.
Project: Autônoma.app
Database: [coloque aqui o link do seu banco Neon]
Environment: Production
Thanks in advance
— Kadu Costa
