Hi all,
With the new historian currently implemented for QuestDB, are there plans from the Inductive team to build support for TimescaleDB and InfluxDB as well? Or would it make more sense for us to develop these modules ourselves?
Timescale already works, why do they need more support?
The new historian enables aggregation in the database, so you'd be able to use powerchart with aggregation in the db. You'd need a module to actually do those aggregations in the db.
The new historian also doesn't do clustering or redundancy, nor does it do standard durability. It is fast, but at the cost of reliability. It is not a "better" system, just an upgrade to the ailing SQLite internal historian option for people not wanting to use an external database.
1 Like
I'm sorry, I'm not actually talking about the new historian, but about the new historian API. I agree with your statement if you're looking to use an internal historian.
The new historian api is superior to the old historian api in many ways. It will enable tools like influx, questdb, timescaledb to be used in their full power, because you're able to do aggregation on the database itself, instead of always querying the raw data and doing aggregation in Ignition.