Repository navigation
Replies: 5 comments 1 reply
|
Hi! Seeing stoolap for the first time. Looks pretty cool. I've recently been rethinking my stance on supporting multiple DBs. Note that adding another DB isn't as simple as just flipping a flag in an ORM. Besides vanilla SQL, TrailBase requires deep understanding of the schemas (for e2e type safety and asserting invariants) as well as change subscriptions. In other words, there's significant cost. The thing is that stoolap seems to be very similar to SQLite (as opposed to something like Postgres), it probably wouldn't make sense to support both. One could argue, why not just use stoolap all-in? If it supports all the features (e.g. change subscriptions), maybe. That said, it looks still pretty young so switching everything over would probably be a significant risk. Anecdotally, TrailBase started out building on Turso and got burned :hide:. That's not to say that stoolap doesn't look very sweet. Are there specific benefits you're hoping for? |
|
Thanks, I totally understand. |
|
just reading up on dbs today and found their turso (re. #162) comparison in stoolap/stoolap#8:
|
Great find - appreciated! With PG in place now, we're in a much better place now to adopt other SQL backends. Would have to look a bit more in detail as to what aspects may or may not be supportable (e.g. realtime subscriptions don't work with PG at the moment. |
|
wanna convert this to a discussion to make it searchable? fwiw I'd love to see "sqlite++" someday but you already smoothed over many rough edges:
I've been looking for "supabase lite" over the years and those features are unique:
|
Uh oh!
There was an error while loading. Please reload this page.
Just an idea, maybe you would like to also integrate the new Rust database
Stoolap.Check:
All reactions