Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96780 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90087 invoked from network); 8 Nov 2016 22:03:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Nov 2016 22:03:45 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 185.153.204.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 185.153.204.214 mail4-2.serversure.net Linux 2.6 Received: from [185.153.204.214] ([185.153.204.214:40846] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 80/97-23587-FBB42285 for ; Tue, 08 Nov 2016 17:03:44 -0500 Received: (qmail 8034 invoked by uid 89); 8 Nov 2016 22:03:38 -0000 Received: by simscan 1.3.1 ppid: 8026, pid: 8030, t: 0.0465s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.7?) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 8 Nov 2016 22:03:38 -0000 To: internals@lists.php.net References: <46.92.05967.9AB91285@pb1.pair.com> Message-ID: Date: Tue, 8 Nov 2016 22:03:36 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] DateTime microseconds discussion From: lester@lsces.co.uk (Lester Caine) On 08/11/16 12:46, Derick Rethans wrote: >> Support for microseconds was added late in the 7.1 RC cycle, however is has >> > some issues: > Some *additional* support for microseconds was added in the PHP 7.1 > cycle, mostly to support bug fixes that have been around for a long > time. We had a similar problem when the resolution of time from Firebird was increased from milliseconds to microseconds. A lot of code that was expecting no sub second time started breaking because of the extra detail. The fix was 'CURRENT_TIME [(precision)]' but a compromise on defaults results in CURRENT_TIMESTAMP != CURRENT_DATE + CURRENT_TIME unless you actually set precision of both to match. On PHP it was actually less of a problem because the data returned has to be converted into a string and ibase.timestampformat filtered the fractional part anyway, and even the seconds can be trimmed if appropriate, so a 'default' string format would solve the problem of comparing time data from different sources? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk