|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #75324 No provision for milliseconds in timestamps
Submitted: 2017-10-06 01:39 UTC Modified: 2021-03-31 11:39 UTC
From: dmiller at amfes dot com Assigned:
Status: Suspended Package: InterBase related
PHP Version: 7.0.24 OS: any
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Bug Type:
From: dmiller at amfes dot com
New email:
PHP Version: OS:


 [2017-10-06 01:39 UTC] dmiller at amfes dot com
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


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2018-03-03 00:32 UTC] keymaker dot 7 at gmail dot com
Tambien se puede cambiar a varchar para obtener la fecha completa:
 [2021-03-31 11:39 UTC]
-Status: Open +Status: Suspended
 [2021-03-31 11:39 UTC]
The interbase extension is moved to PECL[1] as of PHP 7.4.0, and
is looking for a new maintainer.  Until a new maintainer is found,
I suspend this ticket.

Consider to use the bundled PDO_Firebird extension, or the
php-firebird package[2] instead.

[1] <>
[2] <>
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Thu Jun 30 08:05:45 2022 UTC