Re: Multiple data sets in MySQL stored procedures

[derby]

<rant>Our database developers are notorious for creating stored procs that return multiple result sets ... it makes my skin crawl. Multiple result sets violate cohesion principles (do one thing well). Whenever I bring this up, the answer always seems to be - "well we need to reduce network latency." To me, that's a premature optimization and although that may have been true 10 or more years ago it really isn't a problem for most (for my company) today.</rant>

Okay ... sorry for the rant ... back to your normal viewing.

[mpeppler]

There are situations where a stored proc that returns multiple result sets makes a lot of sense.

Then there is the Sybase way, where not only stored procs, but normal SQL batches including lots of requests can be sent to the dataserver with one single request, followed by a simple loop to fetch the results.

This makes client-side programming elegant, as I can throw a Transact-SQL block with IF and WHILE clauses at the server and not have to add any special code to handle it.

Michael

[Herkum]

Consistently I have found( in general not just IT) that most people are intellectually lazy.

Once they find some way of doing something they will not attempt to find another way to do it. Often they will say or do 'ANYTHING' to keep from changing their habits or their thoughts on particular subjects/processes or methods.

In your case, I bet if you ask them for details so that it can fixed, you will get an amazing amount of information and stories that will keep you running-around on why it is an issue.