Bug #5842 Query results are wrong after first null field (System.DBNull)
Submitted: 1 Oct 2004 9:04 Modified: 4 Oct 2004 22:26
Reporter: Benjamin Arroyo Email Updates:
Status: Duplicate Impact on me:
None 
Category:Connector / NET Severity:S1 (Critical)
Version:1.0.0 OS:Microsoft Windows (Windows 2000 SP4)
Assigned to: Assigned Account CPU Architecture:Any

[1 Oct 2004 9:04] Benjamin Arroyo
Description:
Requesting query calculated fields if one results "null", the rest rows will be "null".

For example: 

SELECT (A+B)/C, A, B, C FROM tbl

If C=0 at first row, it returns a System.DBNull field at first Column. And the rest rows at that colum are also System.DBNull although C is not equal to zero at that row.

How to repeat:
Lauch the previous example using the connector with this table:

insert into tbl (A, B, C) values 
(5, 2, 0), 
(2, 4, 1), 
(6, 7, 5), 
(9, 4, 2);

Suggested fix:
¿?
[4 Oct 2004 22:26] Reggie Burnett
This issue has already been reported and fixed.  Thanks!