On Mon, Mar 24, 2003 at 11:50:51AM -0500, Rudy Lippan wrote: > > > > > > - I'd really like to see mysql_client_found_rows=1 being the default. > > > > > > With mysql_client_found_rows off, normal application code can't > > > tell the difference between an update that failed to match a row > > > and one that matched a row but didn't actually change anything. > > D'oh. I just wrote something that did that :( I think you just saved me > from having to track down a bug when I start testing that function. Thanks > Tim :) > > It looks like the only question is one of backwards compatibility. Maybe > we throw a warning in the next version or two, and change after that?
I don't think it's worth it (even assuming you could work out how to "throw a warning" for "it"). Just flag the change of default behaviour clearly in the docs, changes, and release announcement. Tim.
