Databases are the endgame for data-oriented design

Re:Databases are the endgame for data-oriented design by whstl on Wednesday December 06, 2023 @04:19PM (#38549606)

If your colleagues are not applying basic engineering rules to views and stored procedures, it's not fair to say that this is a problem with views and sprocs.

They can and should most definitely be testable, documentable, trackable and version controlled.

Should one also judge all backend programming by PHP standards circa 1998?

[ Parent | on HN ]

Re:Databases are the endgame for data-oriented design by FridgeSeal on Wednesday December 06, 2023 @04:24PM (#38549664)

I tend to judge things by the average-worst-case that they enable and how easily things go wrong, and IME stored procs specifically, go badly real quick.

[ Parent | on HN ]

Re:Databases are the endgame for data-oriented design by ttfkam on Thursday December 07, 2023 @08:42PM (#38564360)

Data structures can be a hard part of programming. That doesn't mean folks don't chose the wrong data structures all the time in any language.

An array instead of a linked list or vice versa. A dequeue instead of a set or vice versa. A binary tree instead of a B+ tree. You can't just throw column names at a DB schema and hope for the best. There's actual engineering to be done, even if many programmers refuse to admit it when interacting with a relational database engine.

[ Parent | on HN ]