This is very cool. Looking forward to the C/++ backend. To me the biggest limitation is that it’s an in-memory data store. I know this is a viable way to run a database, but it’s not ideal for client-side stuff where you can’t just tell your end users to shut up and buy more RAM (or rather, you can but they’ll just jump ship to a different app that doesn’t slow down or crash.)
So I’m musing about how to tie this language into a disk-based database. Its data model seems well suited to a column-oriented DB. I’ve got some experience building higher level abstractions atop low level k/v stores like LMDB so this is tempting … but I’ve already got another project taking up all my spare time.
How far does one have to navigate the docs before seeing some code?
You only have to click on the well-named “Introductory example”, in the upper-left corner.
This is very cool. Looking forward to the C/++ backend. To me the biggest limitation is that it’s an in-memory data store. I know this is a viable way to run a database, but it’s not ideal for client-side stuff where you can’t just tell your end users to shut up and buy more RAM (or rather, you can but they’ll just jump ship to a different app that doesn’t slow down or crash.)
So I’m musing about how to tie this language into a disk-based database. Its data model seems well suited to a column-oriented DB. I’ve got some experience building higher level abstractions atop low level k/v stores like LMDB so this is tempting … but I’ve already got another project taking up all my spare time.