On 12/26/2016 10:35 PM, Wietse Venema wrote: > John Fawcett: >> so long as the loop continues in the presence of a zero return >> code from mysql_next_result() and mysql_store_result is called for >> each one we will stay in sync. With the break above we will be ok, >> since the loop stops only when there are no more results -1 normal >> condition from mysql_next_result or >0 error condition from >> mysql_next_result via the break. > I further reduced the number of state variables, moved the "no > result" check out of the loop, included the database name in warning > messages, and added support for "require_result_set = no" to avoid > the need for dummy SELECT statements in stored procedures. > > Please check out postfix-3.2-20161226-nonprod. As you will see, > code diffs not useful at this point. > > Wietse
Thanks. I ran it through my tests and it produces expected results for queries and stored procedures. I'll run it for a while (using queries) and report back any issues. John
