Bug #7569 Updated: Transmuting indices

ID: 7569 Updated by: danbeck Reported By: ignacio@openservices.net Old-Status: Analyzed Status: Closed Bug Type: Documentation problem Operating system: PHP Version: 4.0 Latest CVS (01/11/2000) Assigned To: Comments: Not really a documentation issue. Using NULL fields in a database is just bad... but I'm a doc writer.. so take it for what it's worth. Previous Comments: --------------------------------------------------------------------------- [2000-11-03 14:45:30] joey@php.net Either false or NULL is the only sane thing for PHP to get in such a case. "" *is not* the same as null, they are very different from the DB's point of view. I think perhaps this one should be closed, but will defer to anyone who feels really strongly one way or the other. --------------------------------------------------------------------------- [2000-11-02 06:39:47] waldschrott@php.net I can´t verify if mssql functions are wrong, it´s not installed here, every function decides itself how to convert or not to convert, but basically these 4 are not equivalent $row=array(1=>NULL,2=>FALSE,3=>"