When microsecond timing becomes the standard it will be very confusing for people to know about the 10 minute boundary. I think it should either be a float or use the current implementation of microseconds. For backwards compatibility with stock mysql float is probably the best choice.
-- microslow patch long_query_time backwards compatibility? https://bugs.launchpad.net/bugs/288062 You received this bug notification because you are a member of OurDelta- developers, which is the registrant for OurDelta. Status in OurDelta - Builds for MySQL: In Progress Bug description: Check percona/microslow patch to be backwards compatible, so an existing user upgrading to OurDelta won't see changed behaviour by default. The my.cnf options are processed and assigned automatically so we probably can't get in there. But before it's used, we can see if it's say < 600 (10 minutes in old form!) and do *1000000 to convert it to microseconds. Should be perfectly safe. _______________________________________________ Mailing list: https://launchpad.net/~ourdelta-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~ourdelta-developers More help : https://help.launchpad.net/ListHelp
