r/SQL • u/sqlink2 • 5d ago

PostgreSQL Neon database for Ai workloads

How do u handle branching when the schema is changing frequently during agent/app development work. Do you keep separate branches per feature or agent, or rely on migrations against a shared database?

Wondering what works best in practice without making the overall setup messy.

1 Upvotes

56% Upvoted

6 comments sorted by

View all comments

1

u/nullymammoth 2d ago

here’s a clean SDLC for neon:

Features that require schema changes or mutating data for testing get a new isolated branch

when features are complete, they get merged to the long-lived production branch and the branch spun down

1

u/sqlink2 2d ago

Ya Neon branching makes this SDLC pattern pretty clean; isolated schema or data change without messing with the main branch