Repository navigation
Unexpected behavior of the Next() method in SessionDataSet #55
Description
In the current version of the library, the Next() method behaves incorrectly. In certain cases, values are added to the Measurements collection that should not be included.
For example, when executing a SELECT * FROM root.raw.droot.test.test_device WHERE time >= 1773618600000 and time < 1773621600000 ORDER BY timequery, the first record contains the has_signal___int measurement, even though according to the query result, it should not be present.
Activity
Fix SessionDataSet: row count, async dispose, and null measurement is…
HTHou commentedon Apr 28, 2026
Thanks for reporting this. This has been fixed in #56, which has been merged into main.
GetRow()now checks whether a TsBlock column is null before calling type-specific getters, so null-valued value-type measurements such asBOOLEAN,INT32, andDOUBLEare no longer incorrectly added toRowRecord.Measurements.