3 ms·
There are two parts to the schema change, the table changes (migrations) and the code changes. I think the person you were replying to was asking about the code
by travisjungroth 4y ago
There are two parts to the schema change, the table changes (migrations) and the code changes. I think the person you were replying to was asking about the code part. Every ORM I've used or looked at[0] does that automatically in the sense that you make a change to a model and all queries generated by that model will now have that change. Depending on the change they could break, but the point is the changes propagate. If you're not using an ORM and are just using string templates, this won't happen. There are query builders, too, which are sort of in between.
[0] Django, SQLAlchemy, Active Record, Piccolo, Tortoise, SQLModel, peewee
- akprasad 4y ago^yes, that's indeed what I had in mind, and you've articulated the position very clearly.
- travisjungroth 4y agoThanks, I’m glad! It’s a topic that pops up for me a lot. Related: https://news.ycombinator.com/item?id=26905647 https://news.ycombinator.com/item?id=26905647