Confirming exclusive Neon DB reads after migration with Prisma
Hi Neon team
I'm using Neon PostgreSQL with Node.js + Express + Prisma in my project Autônoma.app, hosted on **Railway, and I need a technical confirmation regarding data cache and database reads.
I recently completed the full migration from a local JSON-based database to Neon via Prisma, but noticed that the app was still reading some “phantom” or cached data even after a full deploy on Railway.
Following that, I applied all Railway support recommendations: - Added res.set('Cache-Control', 'no-store') to the Express server. - Completely removed old local files (e.g., profissionais.json). - Enforced exclusive use of Neon DB in schema.prisma. - Performed a clean deploy, which is now successful( confirmed in production).
Now I’d like your help confirming these three points:
How can I ensure that the app is reading only from the Neon DB, and not from any cached or old instance? Is there a recommended way to clear cached or residual data on Neon (similar to a full TRUNCATE + restart of sequence IDs)? Does my current plan (likely Free) include automatic backups, and how can I check or restore them if needed?
Additional info: - Project: Autônoma.app - Environment: Production (Railway) - Database: PostgreSQL (Neon) - Prisma connected with SSL
Thanks in advance for your help and support — Kadu Costa (Autônoma.app) @Neon Team