Re: LibCurl 4 and SQLite 3 wrappers
- Posted by petelomax Aug 30, 2019
- 1042 views
jimcbrown said...
petelomax said...
You can store exact atom values, rather than to-nearest-human-readable-string for one, which could be important for a table of thousands of readings.
I don't get it. Why can't you do this with the appropriate number field in SQL? MySQL for example supports FLOAT and DOUBLE columns.
You're not wrong, my bad! How about this: while bind_double() will do only one atom, bind_blob() can do several hundred or more in one go?
I have also just remembered a case where there were 72 meter readings per day, and needing 72 unique column names was quite the pita (a1..24, b1..24, and c1..24, or somesuch).