Working on @xtdb_com #ToolsForThought obsessive, 4GL maximalist (SQL is alright), always happy to chat :)

UK
Filter
Exclude
Time range
-
Minimum likes
XTDB is built for a world with ever increasing regulation and scrutiny over decision making - making data and applications transparent to users and developers alike. Register now if you'd like to hear more zoom.us/webinar/register/461… 2/2
2
3
181
I'm giving an online tech talk with @FINOSFoundation this Wednesday (4pm GMT) on 'as-of reporting' in financial services - but really this applies to all organisations who care about the auditability of systems. XTDB helps you to quickly figure out how data has changed and why /1
1
4
8
528
Replying to @qianl_cs
Rather coincidentally I'll be just across town talking about "bitemporal" SQL:2011 in @xtdb_com not even 2 hours after your talk finishes 😆 events.linuxfoundation.org/o…
1
6
454
Lest we forget "Amazon Redshift is based on an older version of PostgreSQL 8.0.2"
2
4
325
Replying to @sarahcat21 @_Felipe
Arrow is playing a long game. Creating simple things is hard work, but ultimately worth the effort (although ideally you can capture some of the value along the way!). The long-term benefits of simplicity in software development are notoriously underrated: infoq.com/presentations/Simp…
1
78
This one was a really enjoyable chat - jOOQ is an impressive project that has been delivering typesafe & SQL-centric database goodness for far longer than most developers have cared about such things. Good ideas stand the tests of time 🏆
1
10
2,090
I'm hoping to figure out whether Option 3 is worth investigating further in the near future - advice & introductions would be welcome 🙏
1
2
223
Model training requires accurate history, right?
1
5
513
Replying to @refset @paulgb
Ultimately though I suspect the 'best' protocol will be very data & situation dependent. It feels like all the same set of trade-offs you face when thinking about optimal LSM-trees and compression more generally
2
272
Replying to @dbrogdon
SQL
Replying to @refset
(me) Best: Declarative programming at scale. "SQL is the only ever successful, mainstream, and general purpose 4GL." - @lukaseder Worst: Accidental complexity in the language design has created a huge barrier to entry for new RDBMS implementations, which has stifled innovation
2
2
1,219
Replying to @reneeshah123
Surely some database team somewhere is playing with aws.amazon.com/hpc/efa/ already...
3
414
Although even this diagram doesn't cover everything - @jarohen was explaining to me last week how SELECT can take effect both before _and_ after ORDER BY
3
178
Replying to @paulgb
You know SQL literally just turned 50 today, right? 🥳
1
1
193
Replying to @0xgib
By a couple of years it seems, yep. And LISP was already 14 by 1974. What an era it must have been to experience!
3
55
Just in case anyone was in doubt about the stability argument, Q1 (1974) still works great: dl.acm.org/doi/pdf/10.1145/8…
4
535
(my guesses for @frankmcsherry 🤞) Best: A stable, established language that is also conveniently amenable for composing interactive dataflows Worst: WITH RECURSIVE materialize.com/blog/recursi…
1
2
654
(me) Best: Declarative programming at scale. "SQL is the only ever successful, mainstream, and general purpose 4GL." - @lukaseder Worst: Accidental complexity in the language design has created a huge barrier to entry for new RDBMS implementations, which has stifled innovation
3
1
8
3,338
SQL is turning 50 years old later this week 🎉 In your opinion, which are the best bits? Which are the worst?
5
23
94
15,602