161–167 of 167 posts
Earlier quoted context omitted.
Would also store on MicroSD.
That’s part of the problem. Power loss during SD card write will, more likely than not, cause corruption - FAT file systems do not have journaling.
So I tried a simple query in the live demo and it seems that the WHERE clause isn't filtering anything. Am I missing something? SELECT * FROM part WHERE p_size = 7;
Any GUI Client to explore data?
Earlier quoted context omitted.
It would! But it would also be a security nightmare. Exploit SQLite and you could use it in Safari, Chrome and Firefox - everybody could be affected.
Ironically, all the IndexDB implementations were just thin layers on top of sqlite last I checked.
Earlier quoted context omitted.
I'd note that when moving from pg to $other the thing that really trips me up isn't the syntax changes, it's the lack of ARRAY and ROWTYPE. I'm not sure whether those are in scope for you but it'd be nice if the docs said "to be implemented" or "out of scope" somewhere ... and my apologies in advance if they do and I somehow missed it.
We already have support for LIST and STRUCT (which I think are equivalent to ARRAY and ROW, respectively). There is still some functionality missing there (notably storage, and several functions) - but the base functionality is there and the remainder definitely will be added.
Struct looks 10x uglier but perfectly easy to generate, mind, but the whole thing is non-trivial to find :/
Earlier quoted context omitted.
If everything you said is accurate, somebody should make another pitch for WebSQL ( https://en.wikipedia.org/wiki/Web_SQL_Database ) with a custom version of DuckDb! Every browser maker was interested in implementing it but the W3C couldn't go ahead with it because everyone chose to implement it using SQLite, where as W3C required more than one db back-end implementation to move forward.
This could work if there is a subset of SQL where duckDB and SQLite behave almost identically
Earlier quoted context omitted.
This could work if there is a subset of SQL where duckDB and SQLite behave almost identically
I often wondered why someone didn't do it with BerkleyDb too? I know Oracle owns it, but it is open source and someone like Mozilla could have implemented it in their browser just to get the W3C rolling on WebSQL.