Comment by ameliaquining
16 hours ago
Stored procedures have the wrong versioning model. If they were version-locked to the application code, instead of to the database schema, they'd be less of a pain and people might be more willing to use them.
16 hours ago
Stored procedures have the wrong versioning model. If they were version-locked to the application code, instead of to the database schema, they'd be less of a pain and people might be more willing to use them.
Oracle has a feature called 'editions' that does this. Different DB sessions can have different versions of redefinable objects like stored procs and packages.
There are CI/CD processes for deployment, versioning problem is solved at least for 30 years.
Also it is hardly any different from handling version differences in distributed systems, or split between frontend and backend on Web applications.