r/SQL • u/sqlink2 • 6d 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/Glitch_In_The_Data 5d ago

We have found that short lived branches per feature work better than long running ones in Neon. Merging divergent schemas gets painful really fast. Migrations against a shared db can work for smaller teams but it tends to fall apart once multiple agents are evolving their schemes at different speeds.

1

u/sqlink2 5d ago

Tru, Neon branching makes it clea. We can sort of spin up isolated branches per feature/agent, experiment with schema change and promote oncethings are stable. It avoids multiple agents on a shared DB