refset

26 ms·

331.
by refset 3y ago
Except updating in place is almost never what is actually happens outside of RAM - there are usually various layers of Copy on Write happening anyway. So unless your database (or the high-churn subset) cleanly fits in RAM I would generally
332.
by refset 3y ago
> Update is the same as Delete+Create I gave a talk titled "UPDATE Considered Harmful" featuring exactly this idea a few months back. The etymology still makes no sense to me...they should have named it REPLACE instead of UPDAT
333.
by refset 3y ago
Just noting that the documentation found at your first link is much easier to skim by clicking on the parent section - i.e. https://www.swi-prolog.org/pldoc/doc_for?object=section(%27p...
334.
by refset 3y ago
Indeed, Postgres may be wildly popular these days thanks to being $free, but it's far from being the most intelligent relational database engine on offer.
335.
by refset 3y ago
From the extension readme: > Currently, Temporal Tables Extension supports the system-period temporal tables only. For anyone looking for full application-period support and bitemporal tables on Postgres, I think the only actively mainta
336.
JUXT Cast Special with Kent Beck(juxt.pro)
1 points by refset 3y ago|1 comments
337.
by refset 3y ago
The latest JUXT Cast episode on bitemporality, XP, the state of Agile, and developer safety. Available across various podcast platforms: https://pnc.st/s/juxt-cast/736d5a29/juxt-cast-special-with-k...
338.
by refset 3y ago
If you're looking for something novel that combines crypto and ~Clojure, look no further: https://convex.world/
339.
by refset 3y ago
Not disagreeing, and it's only one aspect of Phoenix, but it might be of interest to someone reading that this LiveView-like Clojure library exists: https://github.com/tatut/ripley Also this is a neat list of Live
340.
by refset 3y ago
GitHub link: https://github.com/redplanetlabs/twitter-scale-mastodon Their announcement email reads... > We've open-sourced our Twitter-scale Mastodon implementation on our Github. The implementation is 10k lin
341.
Rama 10k LOC Twitter-scale Mastodon implementation(twitter.com)
6 points by refset 3y ago|1 comments
342.
by refset 3y ago
The presence and use of column families is only half of the puzzle - it doesn't strictly imply that the execution engine is capable of working in a vectorized columnar style (which is necessary for competitive OLAP).
343.
by refset 3y ago
This feels like a promising angle for pursuing alternatives: https://substrait.io/ - "Cross-Language Serialization for Relational Algebra"
344.
Bitemporality and the Art of Maintaining Accurate Databases [video](juxt.pro)
1 points by refset 3y ago|0 comments
345.
by refset 3y ago
When John's co-founder Chuck Geschke died a couple of years ago there was a similar thread posted here [0] and someone in the comments mentioned this 2011 CMU lecture by Chuck, "The Adobe Story", which was a pretty great over
346.
by refset 3y ago
I'm not convinced about that comparison. MongoDB entirely disregarded the relational model whereas bitemporality—as envisioned by Snodgrass et al. and standardised in SQL:2011—is merely an extension/evolution of it. > it would
347.
by refset 3y ago
I mostly agree, but it's the same as the argument for immutability in systems more generally: if you can afford the RAM / GC / storage costs then great. Eventually though costs will decrease and new systems will routinely cap
348.
by refset 3y ago
Makes sense, payroll are usually the last people to find out when somebody's salary has changed :) Which databases have you used for it? Any tips?
349.
by refset 3y ago
Except making n-dimensional indexes both fast and scalable is hard. Often its safest to build your way up, one index at a time, until you fully understand the workload requirements.
350.
by refset 3y ago
Probably this post: https://vvvvalvalval.github.io/posts/2017-07-08-Datomic-this... > If you're new to Datomic, you probably have the same misconceptions as I did regarding the use of Datomic's historical
351.
by refset 3y ago
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
352.
by refset 3y ago
[Re-posting my comment from yesterday https://news.ycombinator.com/item?id=37000572 ] > Part of the reason it hasn’t taken off is because of the additional complexity it imposes on programmers. My take is that it's s
353.
by refset 3y ago
> Part of the reason it hasn’t taken off is because of the additional complexity it imposes on programmers. My take is that it's specifically the additional complexity it imposes on _database_ programmers - the impacts across storag
354.
by refset 3y ago
Hi, I am running a webinar on the concept of bitemporal data management next week, as in https://en.wikipedia.org/wiki/Bitemporal_modeling - please sign up up here if you are at all interested: https://atten
355.
by refset 3y ago
Likely of interest: https://neilmadden.blog/2022/02/19/is-datalog-a-good-languag... (Feb 2022 discussion: https://news.ycombinator.com/item?id=30400886 )
356.
by refset 3y ago
> Databases often provide a time travel feature where we can query AS OF a certain date. This is a good overview of SQL:2011 temporal functionality support across the major players: https://illuminatedcomputing.com/posts&
357.
by refset 3y ago
Old but relevant discussion about pulling out the MVCC data from Postgres to mimic Datomic: https://news.ycombinator.com/item?id=4448189
358.
Simon Wardley: Crossing the River by Feeling the Stones (2018) [video](youtube.com)
1 points by refset 3y ago|0 comments
359.
by refset 3y ago
Great talk! An earlier glimpse of this Decision Matrix process was discussed during the 'Lessons Learned' talk by Alex Miller (2019), specifically "Enumerate Alternatives and Tradeoffs" - https://youtu.be&#x2F
360.
by refset 3y ago
1, 2 and 4 are not to be trusted ;)

More ›