Comments on: Once upon a timestamp(milliseconds)….

By: Darren Cassar

Darren Cassar — Sat, 24 Jul 2010 03:49:07 +0000

With decimal(17,3) you can store the full timestamp including milliseconds. You can then retrieve the date and time (with millisecond) using select timestamp(columnname) from table where columnname is decimal (17,3)

By: minghan

minghan — Mon, 28 Jun 2010 21:08:20 +0000

Why is the reason for using 17 in DEC(17,3)? Thanks!

By: ChangeData

ChangeData — Wed, 21 Apr 2010 15:55:09 +0000

Hi,

I’ve found a possible work around to this. Page 230, in a book called “High Performance MySQL”, lists a User-Defined Function (UDF) called “NOW_USEC” this UDF creates a string in the same format as MySQL date, but also includes millisecond precision. The UDF is also listed here (along with installation details):

http://www.xaprb.com/blog/2007/10/30/how-i-built-the-now_usec-udf-for-mysql/

I have compiled and linked this UDF to my server and works perfectly. To store the value returned by NOW_USEC() just create a field with data type: varchar(26). I know you’ll have to re-link this UDF every time you upgrade your MySQL server, but it’s the best solution I’ve seen so far.

By: Darren Cassar

Darren Cassar — Fri, 07 Aug 2009 18:50:16 +0000

You might want to have a look at: http://blogs.mysql.com/peterg/2009/08/07/fractional-seconds-precision-in-mysql-datetime-data-types/ to learn more about the progress from MySQL’s side.

Cheers,
Darren

By: MySQL :: New Features In MySQL 6.x

MySQL :: New Features In MySQL 6.x — Fri, 07 Aug 2009 16:48:50 +0000

[...] This has been around for a long time, and will be around for a long time. But I did think it’s at least time that we should let people know that we think about it. The specific impetus today was a fairly thorough survey of the feature request’s history in a MySQL DBA’s blog posting Once upon a timestamp(milliseconds)…. [...]