I noticed: http://askmonty.org/blog/the-2-year-old-mariadb/ The support for
microseconds in TIMESTAMP, DATETIME, and TIME.
I fully agree the 'full seconds support only' has been a sever limitation in
MySQL. But I have two concerns with ths:
1)
'noisyness'. On not very fast systems the last
Hello,
By default, the existing precision is used. Only if a column is defined as
TIME|TIMESTAMP(N) with N being either 3 or 6 , then millisecond or
microsecond precision will be used.
Philip Stoev
- Original Message -
From: Peter Laursen peter_laur...@webyog.com
To:
That is fine then! Only a little confusing thing is that as far as I know
TIMESTAMP(14) is supported in MySQL 5.1 (and abandoned in MySQL 5.5) - so
probably still in MariaDB as well. So maybe N should rather have been 17 or
20 (the byte length)?
-- Peter
On Wed, Sep 21, 2011 at 16:39, Philip
@Philip .. I have one more question. Can libmysql as distributed by Oracle
handle those extended precision DATE(TIME)STAMPs - or will only the one
distributed with MariaDB do properly??
-- Peter
On Wed, Sep 21, 2011 at 16:51, Philip Stoev phi...@stoev.org wrote:
That is fine then! Only a
Hi, Peter!
On Sep 21, Peter Laursen wrote:
@Philip .. I have one more question. Can libmysql as distributed by Oracle
handle those extended precision DATE(TIME)STAMPs - or will only the one
distributed with MariaDB do properly??
It should work just fine. We have not changed the API.
Thanks
5 matches
Mail list logo
