Learning is not a spectator sport

I’ve lost track of the number of times I’ve worked with systems that didn’t run brilliantly because every database operation was the “row at a time” methodology.  Typically you see hundreds of routines (either in the database in PL/SQL) or further up the chain in C#, Java etc, and the “alarm bells” start ringing in my head when all of those routines are prefixed with “GET_” and the input parameter looks like a primary key.

It doesn’t take long before the code-reuse mindset starts creating things like:

“for each  EMPLOYEE on screen, call GET_EMP_DETAILS(:screen.employee_number)”

So to try demonstrate the silliness of this… I ask the question:

Would you do this in real life ?

And here’s what happens if you do

https://www.youtube.com/watch?v=-Mlxdn5osvs

🙂