Steve Dinn
@evan I have been in a situation where stored procedures were established by the DBA and consumers of the database used them like an API, so in that case, or if I was intending to provide this kind of "API", then yes. But if I'm developing software and I'm in control of the database, then no.
I find it's a bad code smell if a particular query occurs in more than one place in your app. So using this metric, stored procedures are an unnecessary level of indirection that can lead to obfuscation.
Evan Prodromou
@steve isn't that the point?
Steve Dinn
@evan I've also seen stored procedures go completely off the rails and return completely different result sets depending on the parameter values.
Evan Prodromou
@steve oh, that seems hard to follow. I meant, you pass in an order ID (say) and get only the items for that order. So it performs selection, not projection.
Steve Dinn
@evan By "different result sets" I mean completely different columns and different data not necessarily following the same structure.
Steve Dinn
@evan *Is* that the point? I consider that to be pretty unhinged. If this is the case, why are they not just separate things?
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.