Clojurians Log v2

looking forward to looking through the code! That's how I learned Clojure: looking through the Biff codebase

I was just looking at my old biff app that I no longer deploy and I saw that the master version still uses XTDB1 (can't say it's bad though). Will biff2 have xtdb2 or other DB? Currently I don't see any in the deps.edn: https://github.com/jacobobryant/biff2/blob/master/deps.edn I see hikariCP in this one, so probably no more xtdb? https://github.com/jacobobryant/biff2/blob/master/deps/deps.edn Update: saw the README. Probably XTDBv1 will be used.

@kyle948 that's awesome! let me know if you run into anything that looks weird. of course for any of the libs that aren't released yet/still have unedited AI-generated code, there probably will be plenty of weird stuff ha ha. @invertisment_clojuria the default will actually be sqlite (see https://biffweb.com/p/biff2/ for an explanation of that), and I'll also support/have a lib for XTDBv2. With biff 2 it should actually not be that hard to swap out the DB / have AI generate new "biff DB adapters", e.g. I was planning to possibly also make some adapters for other DBs like postgres, datalevin, https://github.com/xit-vcs/xitdb... and in fact it occurs to me just now that making a XTDB v1 adapter would probably be a really good idea, so existing biff apps could migrate to biff 2 without having to do a DB migration at the same time.

I'm thinking about writing something from scratch. So I don't expect any migration. I already tried to inspect things in biff2 and I saw that with sqlite I'd not have :on-tx like in XTDBv1 but that's probably fine.

nice, that makes things easy. And yeah, neither sqlite or xtdb v2 have a built-in/exposed transaction listener thing like xtdb v1 has. with xtdb v2 you can at least poll for the latest indexed tx ID. I have set up the sqlite adapter so it will call https://github.com/jacobobryant/biff2/blob/f08ac71bda364a757d9137f4d6a9a96df81dded6/libs/sqlite/src/com/biffweb/sqlite.clj#L242 whenever you submit a transaction via com.biffweb.sqlite/execute, so as long as you do all your writes that way, you can set the :biff.db/on-tx key in a biff module to get notified. e.g. the datastar module https://github.com/jacobobryant/biff2/blob/f08ac71bda364a757d9137f4d6a9a96df81dded6/libs/datastar/src/com/biffweb/datastar.clj#L249.

But I'm also thinking whether I want to make it a two-node app or no. I'm not sure yet.

If you do go for a two-node app/want to make it easy to start doing that at any point, any DBs in particular you lean toward? obviously there's xtdb2, or postgres, datomic... I see in #C06MAR553 that datalevin just released support for clusters too.

I'm thinking about making my own notify system in-app with sqlite and then migrating to postgres. But I'll want to keep it extremely low functionality to have less problems later. Yes SSE is what I want but I want to keep it light.

makes sense. probably would make sense for biff to have a postgres adapter anyway.

If you didn't need it it might be that most projects don't outlive xtdb/sqlite

eh. I'm planning to write some kind of specification / guide for writing new DB adapters, and then I'm hoping it won't be that hard to generate them. and IIRC there was in the past interest for using biff v1 with postgres; or at least I assume there was since I wrote a how-to guide for it.