On 11/20/2017 04:25 PM, I wrote: > I've been through this fairly closely, and I think it's pretty much > committable. The only big item that stands out for me is the issue of > OUT parameters. > > While returning multiple result sets will be a useful feature, it's also > very common in my experience for stored procedures to have scalar out > params as well. I'm not sure how we should go about providing for it, > but I think we need to be sure we're not closing any doors. > > Here, for example, is how the MySQL stored procedure feature works with > JDBC: > <https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-usagenotes-statements-callable.html> > I think it will be OK if we use cursors to return multiple result sets, > along the lines of Peter's next patch, but we shouldn't regard that as > the end of the story. Even if we don't provide for it in this go round > we should aim at eventually providing for stored procedure OUT params. > > >
Of course it's true that we could replace a scalar OUT parameter with a one row resultset if we have return of multiple resultsets from SPs. But it's different from the common use pattern and a darn sight more cumbersome to use. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
