3 ms·

I don't see how any of those apply for a two-column 'db' of timestamp and data.

• jmkirby 9y ago
  Except.. compliance staff who want to use some ahem wonderful standards complaint reporting tool. There's just one solitary mention of Informix in the whole discussion, as I'm typing this. And that's a comment lumping Informix with everything else commercial and expensive. I thought Informix owned the embedded dB space at a certain rollout complexity. Remember the backups... Informix speaks json too, including at some quite low level primitives. Whether you buy a product like Informix Edge plus tools or not, depends on what is sending the time series data.
• rpedela 9y ago
  It is database per device and table per sensor, not just one table. With SQL you can do joins, aggregations, etc. If you just want to log it, sure use a log file. As soon as you want to use the data somehow, you need SQL or your own log file parsing and query code. Personally, I rather just use SQL.
  • creeble 9y ago
    If you’re storing from multiple sensors with multiple write processess, you will have concurrency problems if they’re in the same db with SQLite. I’m not referring to manipulating or even querying the data after it’s stored. I just don’t see how saving the original data in SQLite buys you anything, if it needs to be collected into a db for queries, etc, anyway.