Bug #75324 [Com]: No provision for milliseconds in timestamps
| From: | keymaker dot 7 at gmail dot com | Date: | Sat, 03 Mar 2018 00:33:01 +0000 |
| Subject: | Bug #75324 [Com]: No provision for milliseconds in timestamps | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-214189@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=75324&edit=1
ID: 75324
Comment by: keymaker dot 7 at gmail dot com
Reported by: dmiller at amfes dot com
Summary: No provision for milliseconds in timestamps
Status: Open
Type: Bug
Package: InterBase related
Operating System: any
PHP Version: 7.0.24
Block user comment: N
Private report: N
New Comment:
Tambien se puede cambiar a varchar para obtener la fecha completa:
LEFT(CAST(SERVERTIME AS VARCHAR(24)),23)
Previous Comments:
------------------------------------------------------------------------
[2017-10-06 01:39:00] dmiller at amfes dot com
Description:
------------
If a timestamp field is filled with the value of current_timestamp from a stored procedure or
trigger, then the timestamp field will include millisecond information. "Pure" Firebird
queries, such as from Flamerobin, will show the milliseconds. However, queries using the ibase_
functions return using the ibase.timestampformat per the documentation, which uses the strftime
function - which has no provision for milliseconds.
A workaround for the strftime limitation was given in http://php.net/manual/en/function.strftime.php#114532
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=75324&edit=1