Version control might not be a big deal if you are all-in on the database.
Stored procedures are easiest to version by simply defining multiple variants and then incrementally moving the callers in the direction you want. The durability comes from (hopefully) your backups. Point-in-time-recovery is often easier for the business to reason about than a git repository.
was it due to the language expressiveness forcing too much verbosity ? (honest question)
lack of version control, clunky language mechanics, performance issues, etc.
Version control might not be a big deal if you are all-in on the database.
Stored procedures are easiest to version by simply defining multiple variants and then incrementally moving the callers in the direction you want. The durability comes from (hopefully) your backups. Point-in-time-recovery is often easier for the business to reason about than a git repository.
3 replies →
hmm lack of version may be tooled (reminds me of smalltalk, lisp file-less culture)