Here the simplified scenario: We have measurements from a sensor array. The data are checked and plotted. Then they are inserted into an SQLITE database. We find out that after retrieving (selecting) the data back from the database, the plots look different, the data have been changed! First we suspect a problem with our software, but it seems that SQLITE is the culprit!
Occasionally the sensor has a fault or the values are invalid (like negative temperatures). To mark them once and for all as invalid, the faulty values are replaced (in a C environment) by NaNs. Then the data are inserted into the database with a C porgram, in a loop with the sqlite3_bind_double function. The date are retrieved in a loop with the sqlite3_column_double function. It turns out that SQLITE has quietly turned our invalid data (NaNs) into valid 0.0 values! Is this a bug? /Stephan _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
