@voidabyss

I am not understanding what your question is.

My point is that problems can be addressed in the database without forcing regression testing of the external code. If a problem is found in the externsl code, then, even after testing, the updated external code still has to be rolled out to the field.

Maybe it is just me, but I prefer to fix a problem in a specific known place and avoid rollout headaches.