News for hackers. Stuff that matters.

A comment on TimescaleDB 2.0 released, now distributed multi-node. Parent comment

Re:TimescaleDB 2.0 released, now distributed multi-node by mfreed on Thursday October 29, 2020 @02:17PM (#24933501)
Yes, works with SQLAlchemy. (Like many ORMs there are a couple things to be aware of, but plenty StackOverflow questions about these already :)

And yes, people use it for event sourcing. Often see this in various product analytics use cases.

[ Parent | on HN ]
Re:TimescaleDB 2.0 released, now distributed multi-node by ryanbooz on Thursday October 29, 2020 @02:24PM (#24933619)
Although I can't point to a specific application that's currently using TimescaleDB for an event sourcing service (I assume you're talking about the design pattern), it would be a great use case. Change in state over time is perfect time-series scenario.

As for SQLAlchemy, TimescaleDB is fully PostgreSQL compliant, so it will work out of the box. There will be a few nuances that need to be considered, particularly when writing queries that use some of our additional time-series functions like time_bucket.

But day-to-day ORM CRUD patterns should work as you expect!

[ Parent | on HN ]
Re:TimescaleDB 2.0 released, now distributed multi-node by robertlagrant on Thursday October 29, 2020 @03:27PM (#24934576)
Thank you (both of you!). Agreed - I mean the design pattern, but I was being a bit vague.
[ Parent | on HN ]
Re:TimescaleDB 2.0 released, now distributed multi-node by johnthescott on Thursday October 29, 2020 @04:53PM (#24935703)
are pg extensions supported?

-j

[ Parent | on HN ]
Re:TimescaleDB 2.0 released, now distributed multi-node by mfreed on Thursday October 29, 2020 @05:15PM (#24935998)
Yes, TimescaleDB plays friendly with most PG extensions.

And Timescale Cloud comes pre-loaded with many of them - https://kb.timescale.cloud/en/articles/2754991-supported-pos...

[ Parent | on HN ]