On 21/05/2009, at 12:51 PM, Neil Katin wrote:
> Arjen, I could use some advice on this problem. The "right" fix
> wasn't very clear to me.
> The new variable type is called "double", but its really a fixed
> point number, with
> magic done by sys_var_thd_microtime.
> I'm working on an absolutely minimal patch that just changes the
> assert to all ULL and
> DOUBLE values. But I suspect the name of GET_DOUBLE will confuse
> folks in the future.
Yea it's a practical hack.
You could have a quick peek in the mysql 5.1 codebase, which also
supports fractional seconds for long_query_time.
The implementation is not identical but you may be able to work out
something from that.
I don't remember off-hand what was used there.
Cheers,
Arjen.
--
Arjen Lentz, Director @ Open Query (http://openquery.com)
Affordable Training and ProActive Support for MySQL & related
technologies
Hi Neil
On 21/05/2009, at 12:51 PM, Neil Katin wrote: thd_microtime.
> Arjen, I could use some advice on this problem. The "right" fix
> wasn't very clear to me.
> The new variable type is called "double", but its really a fixed
> point number, with
> magic done by sys_var_
> I'm working on an absolutely minimal patch that just changes the
> assert to all ULL and
> DOUBLE values. But I suspect the name of GET_DOUBLE will confuse
> folks in the future.
Yea it's a practical hack.
You could have a quick peek in the mysql 5.1 codebase, which also
supports fractional seconds for long_query_time.
The implementation is not identical but you may be able to work out
something from that.
I don't remember off-hand what was used there.
Cheers, openquery. com)
Arjen.
--
Arjen Lentz, Director @ Open Query (http://
Affordable Training and ProActive Support for MySQL & related
technologies
Follow our blog at http:// openquery. com/blog/ ourdelta. org
OurDelta: free enhanced builds for MySQL @ http://