I was so excited to try it out it that I just released an in-browser PostgreSQL playground on top of PGlite.
It's also open source and easy to integrate:
6,898 karma · joined December 12, 2016
I was so excited to try it out it that I just released an in-browser PostgreSQL playground on top of PGlite.
It's also open source and easy to integrate:
And if you want to try some code, I've prepared three toy Bloom filter implementations to accompany the article:
JavaScript: https://codapi.org/embed/?engine=browser&sandbox=javascript&...
Python: https://codapi.org/embed/?sandbox=python&src=gist:e7bde93f98...
Go: https://codapi.org/embed/?sandbox=go&src=gist:e7bde93f98c5e4...
> Functions that shrink the size of a slice (Delete, DeleteFunc, Compact, CompactFunc, and Replace) now zero the elements between the new length and the old length.
I haven't tried this though :)
This kind of defeats the idea of interactive code snippets in the docs (but might still be useful in other use cases).
The network may be fast and the traffic cheap in some parts of the world, but not in others.
There is also an "external" mode where you can use a full-featured editor with syntax highlighting, etc. For example:
> does it memoize dependencies?
Not sure what do you mean by memoization here, but there is no stored state at all (see the original post for the reasoning behind this).
> if i have several cells that all depend on a central one, will the central one only run once?
Sure!
> can you declare a variable in one cell then use it in another?
You can, as long as it's in global scope.
> The last thing I want as a reader is code examples that fail or behave oddly because they were run out of order. Or because I didn't run some cells. Or because I changed a cell and didn't re-run it.
> Codapi code cells, unlike Jupyter's, have no hidden state. Instead, they execute the whole chain of dependencies as needed to ensure that the reader gets a consistent result.
What SQL Polyglot can do is help you quickly check if certain database engines support a certain SQL feature.
And yes, I should definitely increase the C# sandbox timeout. Will do :)
I have been talking to Auxten about adding some interactivity to the code examples on doc.chdb.io, so hopefully the chDB docs will soon be even friendlier to newcomers.
Disappointing.