Bug #75324 [Opn->Sus]: No provision for milliseconds in timestamps

Edit report at https://bugs.php.net/bug.php?id=75324&edit=1 ID: 75324 Updated by: cmb@php.net Reported by: dmiller at amfes dot com Summary: No provision for milliseconds in timestamps -Status: Open +Status: Suspended Type: Bug Package: InterBase related Operating System: any PHP Version: 7.0.24 Block user comment: N Private report: N New Comment: 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] <https://pecl.php.net/package/interbase> [2] <https://github.com/FirebirdSQL/php-firebird> Previous Comments: ------------------------------------------------------------------------ [2018-03-03 00:32:59] keymaker dot 7 at gmail dot com Tambien se puede cambiar a varchar para obtener la fecha completa: LEFT(CAST(SERVERTIME AS VARCHAR(24)),23) ------------------------------------------------------------------------ [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