crux
pg_bitemporal
crux | pg_bitemporal | |
---|---|---|
16 | 7 | |
1,475 | 140 | |
- | 1.4% | |
9.7 | 0.0 | |
over 2 years ago | about 2 years ago | |
Clojure | PLpgSQL | |
MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
crux
- Speeding Up `Atan2f` by 50x
-
Bridging the Blockchain / Database Divide (Temporal Graph Queries for Corda)
Hi, a couple of my colleagues spent some time working on this integration with our open source database product (https://opencrux.com), and I'm curious to know - has anyone done similar things to connect Corda with a secondary off-the-shelf query engine?
- Crux 1.18.0 Is Out
-
Crux 1.18.0 is out!
For more details, see the release notes.
-
Looking for Intermediate & Advanced SQL Users for Research
The context is that I work on on https://opencrux.com, which offers a bi-temporal Datalog query layer (as well as SQL) that more or less addresses the intersection of the two, since Datalog is great for expressing recursive queries.
-
How to query Datomic, Datascript, Asami, or other graph databases
I suppose another somewhat important distinction, once again performance related, is that graph databases will typically track index statistics to aid with query planning. For example, Crux uses stored knowledge of attribute-value cardinalities (recently via HyperLogLog) to optimise the join order of a query - this can make a big difference when attempting to traverse large graphs efficiently.
-
Free project to practice sql ?
Agreed, recursive querying & bitemporal modelling in SQL are non-trivial problems, and the combination of the two is harder still. For an alternative perspective on tackling such problems I'd suggest looking at Datalog, which makes recursion a breeze, and a database with first-class bitemporality - both of which feature in https://opencrux.com (which I happen to work on :))
-
Ask HN: What under-the-radar technology are you super excited about?
I work on Crux so can share a few details about our implementation of Datalog. The query is compiled into a kind of Worst-Case Optimal Join algorithm [0] which means that certain types of queries (e.g. cyclic graph-analytical queries, like counting triangles) are generally more efficient than what is possible with a non-WCOJ query execution strategy. However, the potency of this approach relies on the query planner calculating a good ordering of variables for the join order, and this is a hard problem in itself.
Crux is usually very competent at selecting a sensible variable ordering but when it makes a bad choice your query will take an unnecessary performance hit. The workaround for these situations is to break your query into smaller queries (since we don't wish to support any kind of hinting). Over the longer term we will be continuing to build more intelligent heuristics that make use of advanced population statistics. For instance we are about to merge a PR that uses HyperLogLog to inform attribute selectivity: https://github.com/juxt/crux/pull/1472
[0] https://cs.stanford.edu/people/chrismre/papers/paper49.Ngo.p...
- Bitemporal History
- Git as a NoSql Database
pg_bitemporal
-
The Guide to PostgreSQL Data Change Tracking
I feel like i keep yelling the following, but bitemporal tables.
- https://aiven.io/blog/two-dimensional-time-with-bitemporal-d...
- https://github.com/scalegenius/pg_bitemporal
4 timestamps and some ugly queries.
-
Eventual Business Consistency
People here may also be interested to see this analysis of the state of SQL:2011 "temporal table" feature adoption: https://illuminatedcomputing.com/posts/2019/08/sql2011-surve...
I don't think much has really changed since, and I'm not sure Postgres is any closer to addressing this natively (although there have been extensions, e.g. https://github.com/scalegenius/pg_bitemporal).
- Show HN: I made a CMS that uses Git to store your data
-
Record history / Temporal table question
Something more sophisticated would be https://github.com/scalegenius/pg_bitemporal
- PostgreSQL 14 Released
-
Bitemporal History
Sure, I can appreciate that native support for a feature like this is nice.
As I understand it, most implementations (including another one for bitemporality[1]) involve either audit tables, as you mention, and/or additional support columns. It's as if the "now" representation is simply a narrow lens onto the underlying data.
That said, PostgreSQL encodes and has battle-tested decades of database functionality including an ecosystem around those, so I'd be a little wary of switching technology even if it does solve one individual problem thoroughly. Everything has to start somewhere, though.
[1] - https://github.com/scalegenius/pg_bitemporal
What are some alternatives?
xtdb - An immutable database for application development and time-travel data compliance, with SQL and XTQL. Developed by @juxt
temporal_tables - Temporal Tables PostgreSQL Extension
asami - A graph store for Clojure and ClojureScript
Reladomo - Reladomo is an enterprise grade object-relational mapping framework for Java.
specter - Clojure(Script)'s missing piece
wasmer.io - The Wasmer.io website
materialize - The data warehouse for operational workloads.
outstatic - Outstatic - A static CMS for Next.js
mergestat-lite - Query git repositories with SQL. Generate reports, perform status checks, analyze codebases. 🔍 📊
Kirby - Kirby's core application folder
mnm - mnm implements TMTP protocol. Let Internet sites message members directly, instead of unreliable, insecure email. Contributors welcome! (Server)
Publii - The most intuitive Static Site CMS designed for SEO-optimized and privacy-focused websites.