Req #60288 [Opn->Wfx]: ZERO DATES IN STRTOTIME

Edit report at https://bugs.php.net/bug.php?id=60288&edit=1 ID: 60288 Updated by: heiglandreas@php.net Reported by: it at ezy2c dot com Summary: ZERO DATES IN STRTOTIME -Status: Open +Status: Wont fix Type: Feature/Change Request Package: Date/time related Operating System: CENTOS 5 64 bit PHP Version: 5.3.8 Block user comment: N Private report: N New Comment: On the other hand, checking for "0000-00-00 00:00:00" before throwing the date into DateTime would also solve the issue and be much cleaner. In the end the "0000-00-00 00:00:00" is the databases way of saying "this database-field has a NULL value". And would you pass that to DateTime you'd get the current date which is not what you want. So I'd not see this as a bug in DateTime but in your code when you're passing DateTime wrong information. Adding a further flag that needs maintenance and adds to the complexity of DateTime is IMHO not the right way to handle this. Previous Comments: ------------------------------------------------------------------------ [2012-02-20 21:34:20] it at ezy2c dot com Physically 0000-00-00 00:00:00 is NOT a real date, however all major databases commonly use this as a default datetime value to differentiate between a valid and and an invalid date. ------------------------------------------------------------------------ [2012-02-20 21:01:06] john at gbd dot co dot uk as 0000-00-00 is a non-existant date (the day before 01-01-0001 was 31/12/-0001) then strtotime() should return NULL on all systems ------------------------------------------------------------------------ [2011-11-14 03:17:58] it at ezy2c dot com The Optional parameter could be set to DEFAULT of TRUE, that way it works as it would on 32-bit. However if you want to use a date 292 billion years ij the past or future, specify FALSE. ------------------------------------------------------------------------ [2011-11-14 03:16:07] it at ezy2c dot com Description: ------------ If you could please include a 3rd switch to strtotime ( string $time [, int $now = time() ], [legacy32bit = boolean] ) This would both allow large date ranges as well is be backwards supporting of database default timestamps ie 0000-00-00 00:00:00 they get converted to an ambiguous -0001-11-30 00:00:00. if it was used like this strtotime($DBROW['timestampcolumn'], time(), true) and it returns NULL as it did in the 32-bit version this whole issue could be avoided and it can still support a very large date range. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=60288&edit=1