home.social

#xtdb — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #xtdb, aggregated by home.social.

fetched live
  1. Has anyone done #bitemporal stuff with postgres 16? I understand SQL:2011 support has landed in postgres 18 but I'm hesitant about upgrading (being very conservative). I'm aware of github.com/scalegenius/pg_bite and github.com/xocolatl/periods but I'm no database expert and I feel like a baby engineer dipping my toes in. What do y'all recommend?

    (I don't want to use #xtdb or #datomic because I know even less about these and I want to be able to maintain what I build)

  2. Has anyone done #bitemporal stuff with postgres 16? I understand SQL:2011 support has landed in postgres 18 but I'm hesitant about upgrading (being very conservative). I'm aware of github.com/scalegenius/pg_bite and github.com/xocolatl/periods but I'm no database expert and I feel like a baby engineer dipping my toes in. What do y'all recommend?

    (I don't want to use #xtdb or #datomic because I know even less about these and I want to be able to maintain what I build)

  3. Anyone done work with #XTDB? It looks awesome to me, and the few hours I got to spend playing with it last night only made me more convinced. But obviously a huge difference between trying out a DB for fun and having to maintain one in production. So I would love to hear from anyone with experience in the latter. Or in lieu of that, someone else who have used it for fun :)

    github.com/xtdb/xtdb

  4. Anyone done work with #XTDB? It looks awesome to me, and the few hours I got to spend playing with it last night only made me more convinced. But obviously a huge difference between trying out a DB for fun and having to maintain one in production. So I would love to hear from anyone with experience in the latter. Or in lieu of that, someone else who have used it for fun :)

    github.com/xtdb/xtdb

  5. ```clojure
    (xt/execute-tx
    node
    [[:update '{:table :usage
    :bind [{:xt/id id} user]
    :unify [(from :usage [{:xt/id id} user-id])
    (where (nil? user-id))]
    :set {:user-id user
    :guild-id "98393139101827072"}}]])
    ```

    I wanted to copy user->user-id in records that lack a user-id. Am #xtdb ing correctly? Also filling in guild-id with a static value.

    Took me a while to get this right!

  6. ```clojure
    (xt/execute-tx
    node
    [[:update '{:table :usage
    :bind [{:xt/id id} user]
    :unify [(from :usage [{:xt/id id} user-id])
    (where (nil? user-id))]
    :set {:user-id user
    :guild-id "98393139101827072"}}]])
    ```

    I wanted to copy user->user-id in records that lack a user-id. Am #xtdb ing correctly? Also filling in guild-id with a static value.

    Took me a while to get this right!

  7. Me finally deciding I should try #datomic, going all the way through helloworld only to realize that the "datomic local" flavor doesn’t do stored functions.

    (╯°□°)╯︵ ┻━┻

    So to even try those I'd have to spin up a local postgres, deploy datomic transactor, and figure the pg schema.

    #xtdb looks like fun again.

  8. Me finally deciding I should try #datomic, going all the way through helloworld only to realize that the "datomic local" flavor doesn’t do stored functions.

    (╯°□°)╯︵ ┻━┻

    So to even try those I'd have to spin up a local postgres, deploy datomic transactor, and figure the pg schema.

    #xtdb looks like fun again.

  9. Well, it looks like I'm building another database again.

    This time, it is a database embedded into the MDM tool I'm working on, and it is heavily inspired by #Datomic and #xtdb

  10. At some point (I missed the memo) #xtdb stopped espousing #datalog and invented #xtql. I'm guessing this was to step out of any annoying dependencies of datalog and dampen comparison with the other major datalog approaches in #Clojure.

    docs.xtdb.com/intro/what-is-xt I especially enjoy the side-by-side Clojure/JSON comparisons here

  11. At some point (I missed the memo) #xtdb stopped espousing #datalog and invented #xtql. I'm guessing this was to step out of any annoying dependencies of datalog and dampen comparison with the other major datalog approaches in #Clojure.

    docs.xtdb.com/intro/what-is-xt I especially enjoy the side-by-side Clojure/JSON comparisons here

  12. #git must have been the first successful bitemporal database.

    The commits trees are the domain time, and the reflog is the transactional time.

    It must has been the inspiration to #datomic and #xtdb.

    #git #datomic #xtdb #clojure #database

  13. #git must have been the first successful bitemporal database.

    The commits trees are the domain time, and the reflog is the transactional time.

    It must has been the inspiration to #datomic and #xtdb.

    #git #datomic #xtdb #clojure #database

  14. Have you ever heard of a "bitemporal" database? 🤔

    This week, I'm talking to James Henderson, lead developer of #XTDB, to explore the world of bitemporality and the life of a #database developer.

    Listen: pod.link/developer-voices/epis
    Watch: youtu.be/3sRKQg9-In8

  15. Have you ever heard of a "bitemporal" database? 🤔

    This week, I'm talking to James Henderson, lead developer of #XTDB, to explore the world of bitemporality and the life of a #database developer.

    Listen: pod.link/developer-voices/epis
    Watch: youtu.be/3sRKQg9-In8

  16. "State of XTDB" by Jon Pither
    youtube.com/watch?v=gQV-XrkJj2

    Talk about the current and upcoming evolution of the #XTDB database. The coolest thing about this, to me, is the introduction of the new temporal features and how you're able to query over them. To people who've never used a temporal database before, time travel is mind blowing enough, but what's presented there takes it to a new level. Off the top of my head, I don't have a use case for it, but it sure is interesting.

  17. As cool as I think XTDB is (not the least the upcoming version 2.0), the liberation of Datomic is great news (I've been using it for Meewee with 0 breakdowns since 2012):
    blog.datomic.com/2023/04/datom

  18. It would be fun to tinker with a full reproducible (or ) system build to run .

    The only variable would be the games as downloaded from the point-in-time when running.

    This would provide the user community the benefit of fast, Iterative testing with a parametrized input of software details... Maybe the steam-cli could even non-interactively spin up a game to make sure it bootstraps. Then the game gets a "plus one" from compatibility bot. Or maybe not.

    There is a finite number of configuration options stored in .

    This is how I "do gaming" in my 40s.

  19. It's been a while since I saw the @xtdb @xtdb_com front page, but it's looking great now as I did my first bit of workplace evangelism for the #xtdb database xtdb.com/ . It has potential for university humanities research projects.