in reply to Re: [Semi-OT] Views, Stored Procedures, and Class::DBI
in thread [Semi-OT] Views, Stored Procedures, and Class::DBI

I wouldn't go as far and put stored procedures into the database - this means that the "actual" code is distributed over too many (two) components.

But when you start to have many components consolidating code into the database via stored procedures can simplify the code of many clients.

Perhaps my view is too abstract, but I find the implication that a database's schema and implementation is not code to be limiting. If these limits really exist then fine; but here the discussion is premised on no lock-in to a particular database. Do not needlessly tie a free hand.

Be well,
rir

  • Comment on Re^2: [Semi-OT] Views, Stored Procedures, and Class::DBI

In Section Meditations