On 01/04/15 22:11, Stanislav Malyshev wrote: >> * mysqli::next_result() if there is no next result throws "There is no next >> > result set" > This I'm not sure should produce anything at all - it has the return > value of false, should be good enough.
'Traditional' scanning of a result set on most of the drivers simply takes the false/null as 'end of file' so any exception generated should be able to be switched off. But it's the same discussion as throwing exceptions when an object can't be created. One workflow simply needs the 'null', while an exception based workflow needs the exception? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
