#13549 [Fbk->Opn]: Broken NULL column result condition
| From: | mlemos at acm dot org | Date: | Thu, 15 Aug 2002 01:30:40 +0000 |
| Subject: | #13549 [Fbk->Opn]: Broken NULL column result condition | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-16866@lists.php.net to get a copy of this message | ||
ID: 13549
User updated by: mlemos@acm.org
Reported By: mlemos@acm.org
-Status: Feedback
+Status: Open
Bug Type: MSSQL related
Operating System: Windows 2000
PHP Version: 4.0.6
New Comment:
There is no personal issue here. Assuming that this bug report was was
a support request just showed that you did not pay much attention to
what was reported. Pay attention and test what reported as broken is
what you should have done as your homework.
The issue here is that MS SQL API was modeled after MySQL API a long
time ago in the PHP 3 days. By then there was no boolean type in PHP.
As far as I can recall this function was not return anything then for
NULL columns, just like in MySQL API which does not document this
behaviour.
This problem was spotted by running regression tests that succeed in
MySQL but not in MSSQL. That is why I assumed it can only be a bug,
especially because it could never have returned a boolean value when it
was working as expected.
Setting straight the behaviour of a function that is not completely
documented is not breaking compatibility. Making it work consistently
with the way it was originally based on, is the right way to solve the
issue.
Previous Comments:
------------------------------------------------------------------------
[2002-08-14 09:29:21] kalowsky@php.net
Seeing as this bug was submitted against PHP 4.0.6, and that we are now
at 4.2.2 (a long ways) this is now to be considered a feature thanks to
backwards compatibility.
I haven't seen any other complaints about this functionality, nor have
I heard any. A quick search on google reveals no complaints either. I
did do my homework Mr. Lemos, so please don't turn this into a personal
issue.
If you believe that this should be documented, so be it. Write up the
bit of documentation that you believe is required, and post it inside
this bug.
------------------------------------------------------------------------
[2002-08-13 23:55:52] mlemos@acm.org
This is not a support question.
Do your homework and make it worthy for other developers report any
bugs at all.
It is not documented anywhere what is returned in the row array for
result columns that returned NULL values.
Most PHP API for other databases just return an undefined value for the
column position in the row array. PHP MSSQL API is not consistent with
and so it seems like a bug.
If it is not a bug, document the intended behaviour.
------------------------------------------------------------------------
[2002-08-13 23:36:08] kalowsky@php.net
Sorry, but the bug system is not the appropriate forum for asking
support questions. Your problem does not imply a bug in PHP itself.
For a list of more appropriate places to ask for help using PHP,
please visit http://www.php.net/support.php
Thank you for your interest in PHP.
------------------------------------------------------------------------
[2001-10-04 18:40:32] mlemos@acm.org
What is the condition that determines that a result column has is
NULL?
I thought that the array returned by mssql_fetch_row would return an
unset entry for the given column position but it seems to set it with a
boolean false value now.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=13549&edit=1