Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19301 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96015 invoked by uid 1010); 30 Sep 2005 07:20:03 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 96000 invoked from network); 30 Sep 2005 07:20:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Sep 2005 07:20:03 -0000 X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Linux 2.5 (sometimes 2.4) (4) Received: from ([82.94.239.5:60501] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id AD/37-54476-227EC334 for ; Fri, 30 Sep 2005 03:20:02 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id j8U7JxgB013814; Fri, 30 Sep 2005 09:19:59 +0200 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id j8U7Jvjk013809; Fri, 30 Sep 2005 09:19:58 +0200 Date: Fri, 30 Sep 2005 09:19:57 +0200 (CEST) X-X-Sender: derick@localhost To: Andi Gutmans cc: internals@lists.php.net In-Reply-To: <6.2.3.4.2.20050929073711.0453cd30@localhost> Message-ID: References: <43393A43.4070805@lsces.co.uk> <43397E48.7080107@lsces.co.uk> <43398CB6.9030808@lsces.co.uk> <433ABE48.6050607@lerdorf.com> <6.2.3.4.2.20050928155517.04710860@localhost> <6.2.3.4.2.20050929073711.0453cd30@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at jdi-ict.nl Subject: Re: [PHP-DEV] timezones & date() breakage From: derick@php.net (Derick Rethans) On Thu, 29 Sep 2005, Andi Gutmans wrote: > - In Israel the timezone DB changes every year (we start savings time on > different dates every year depending on the parliament decision). That is incorrect. That was only upto and including 2004. Since 2005 there is a set-rule for it. > I see that > in your implementation this DB is taken from a table written in C. Are you > saying that this table isn't currently being used? Or would I have to update > that C table every year? Ofcourse the table is in use, otherwise it would not have been put in. > All sysadmins in Israel pretty much have an automated way of getting the > updated timezone file from a central distribution FTP server which they just > drop in automatically into the system. Not allowing this to work would be a > serious problem. Israel's probably not the only country with a dynamically > changing DB. Brasil is AFAIK the only other one. > Also, it would require us to roll new PHP versions whenever such > a company changes their DB. So if this is the case, irregardless we should > support the old approach. Or we create a PECL extension that you can install and if it is installed then it uses the timezone database from there. And yes, ofcourse I keep updating the timezone database in CVS as soon as a new one is out. > Anyway, please give some more insight so that the situation is clear. > As stated in my previous email, irregardless, as Wez pointed out having two > sets of APIs is probably a better idea so that everyone is happy. That also means that we're reintroducing about a 20 bugs again. Please remember that the whole idea *why* I started with it was that the code now is broken, even although it might seem to work fine for you. regards, Derick