#21279 [Opn->Bgs]: odbc_fetch_into returns empty strings for columns with NULL values
| From: | kalowsky@php.net | Date: | Fri, 03 Jan 2003 18:10:44 +0000 |
| Subject: | #21279 [Opn->Bgs]: odbc_fetch_into returns empty strings for columns with NULL values | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-28999@lists.php.net to get a copy of this message | ||
ID: 21279
Updated by: kalowsky@php.net
Reported By: mlemos@acm.org
-Status: Open
+Status: Bogus
Bug Type: ODBC related
Operating System: Windows
PHP Version: 4.3.0
New Comment:
Which other API's are you talking about? Oracle? It's the only other
extension that uses fetch into really.
As for the statement, there is no way for ODBC to really tell either.
The API itself defines this to be rather ambiguous so it becomes
difficult to deal with. At this time the result leaves it to the PHP
user to decide if one is really an emtpy string or NULL rather than the
PHP engine. I tend to think this is a better solution.
Previous Comments:
------------------------------------------------------------------------
[2002-12-29 19:47:04] mlemos@acm.org
odbc_fetch_into returns empty strings for columns with NULL values.
This makes it impossible to distinguish whether a result column value
is a real empty string or a NULL, unlike with API functions for the
same purpose but for other databases.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=21279&edit=1