Unexpected behavior of the Next() method in SessionDataSet

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.