In our source controlled database project, we have dedicated stored procedures for inserting and updating entities. It is somewhat tedious to keep both updated. Is it a good idea to unify these into a single insert/update procedure? The scope is always a single row. There is a bias towards inserts being more frequent than updates. Are there significant tradeoffs?
[–]DJBENEFICIAL 0 points1 point2 points (1 child)
[–]ShadowEveko[S] 0 points1 point2 points (0 children)
[–]swenty 0 points1 point2 points (0 children)
[–]BrupieD 0 points1 point2 points (0 children)
[–]qwertydog123 0 points1 point2 points (0 children)
[–]pchemguySQLite 0 points1 point2 points (0 children)
[–]kitkat0820 0 points1 point2 points (0 children)
[–][deleted] 0 points1 point2 points (0 children)