ID:               13793
 Updated by:       erik@[...].com
 Reported By:      smk@[...].com
 Status:           Closed
 Bug Type:         InterBase related
 Operating System: Linux
 PHP Version:      4.0.6
 New Comment:

Has this bug really been fixed? I'm still seeing this behavior in
version 4.1.2. Thanks

--erik


Previous Comments:
------------------------------------------------------------------------

[2002-04-04 07:06:49] smk@[...].com

Glad to hear that it's fixed in the Concurrent Version System
open-standard version. Can you notify me when this fix is rolled into a
standard non-development version/update?

Thanks,
Steve

------------------------------------------------------------------------

[2002-04-03 20:36:43] daniela@[...].net

Already fixed in CVS

------------------------------------------------------------------------

[2001-10-22 18:15:24] smk@[...].com

It seems that, if there is a NULL field at the end of a query string,
or TWO or more NULL fields in the MIDDLE of the QUERY string,
ibase_fetch_row just DROPS the nulls, and any column data that follows
them. For exampe, if I have a table with the columns: FNAME, LNAME, MI,
PREFIX, SUFFIX, DOB, SEX, PASSWORD . . . 
IF MI, PREFIX, and SUFFIX all allow NULL values, and all are null, a
SELECT * on this table would only return TWO values: FNAME and LNAME.
It would leave out the PASSWORD!

This is VERY BAD. It SHOULD return (like in any normal SQL query) null
values for any null fields, and NOT skip or stop at any columns, just
because the data is null.

So . . . I have to populate every field with a default null value (a
space, or the word "null", for example), if I want to make sure not to
miss column date when I do a SELECT statement using ibase_fetch_row.

If anyone knows a way around this, an explanation, or any other ideas,
please post them.
   Thanks, Steve

------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=13793&edit=1