Re: Best way to "CALL ... INTO @a, @b"?

[Peter Brawley]

> "CALL ... INTO @a, @b" does not work.

Indeed, we can't just make up syntax.

> Apart from rewriting the procedures to store the results in OUT/INOUT variables,

That's what OUT & INOUT vars are for.

> what are the preferred ways to extract data from their resultsets into local variables?

If you need to persist parts of a resultset in MySQL memory space for some reason, the alternative is to save the desired results to a temp table.

Most often, though, if a resultset needs to be processed, it'll be done in an application language (PHP, Perl, Java, C# &c), and in those languages retrieval of a resultset already stores result vectors into the app's memory.