Yeah I'm with you on this one. I think they keep these in code so that they can deploy over multiple databases. But I think this should be seen as a schema chan

Yeah I'm with you on this one. I think they keep these in code so that they can deploy over multiple databases. But I think this should be seen as a schema change. If you make a change to a view, materialized view or procedure you need to store that change in git and deploy it out to all instances via a migration tool.