Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82591 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71249 invoked from network); 13 Feb 2015 09:52:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Feb 2015 09:52:37 -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 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:57400] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A2/B1-62214-269CDD45 for ; Fri, 13 Feb 2015 04:52:35 -0500 Received: (qmail 12566 invoked by uid 89); 13 Feb 2015 09:52:31 -0000 Received: by simscan 1.3.1 ppid: 12560, pid: 12563, t: 0.0651s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.189.147.37) by mail4.serversure.net with ESMTPA; 13 Feb 2015 09:52:31 -0000 Message-ID: <54DDC95F.3080102@lsces.co.uk> Date: Fri, 13 Feb 2015 09:52:31 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Legal date generated from illegal date From: lester@lsces.co.uk (Lester Caine) On 13/02/15 04:03, Yasuo Ohgaki wrote: > I see controversial behavior here, unserialize raises error while new > DateTime('0000-00-00') doesn't. > > If it's a bug, I'll just file it as a bug. Yasuo Management of dates is controversial in a lot more areas than just using the wrong calendar in prior times ;) Each database uses it's own way to handle dates and time internally, and most default actions are different, add to which using second as the base for dates is just wrong anyway, but we have to live with what is currently available. The area that needs fixing first is the underlying OS functions rather than continually trying to patch the top level, but we perhaps need to document better just where the joins are ... just how many days were there from 0BC to today ... -- 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