31–40 of 51 posts
Any performance numbers? For instance how might this handle 1M+ records, 15+ columns in a single table?
Love the SvelteKit usage, good job on that departament
I think I broke something. Made a table named pics, attached 2 random images and now clicking the table shows just the row numbers. Everything else is blank, no rows visible, just the indexes.
This is pretty cool! I'm not sure what I would use it for, but it seems like it's definitely useful. I've been in the midst of developing my own frontend (SPA/PWA) data storage solution, using IndexedDB (and the Dexie library), so I've been watching all of the recent announcements about the wasm-sqlite implementations and wondering if I should probably just switch over to that. If, for nothing else, for the exportabl…
I love the idea of an Airtable/Notion open source alternative, but I haven't seen any projects yet that look like a solid long-term bet. NocoDB is neat, but looks like it's a single vendor-driven project that could go open core or die altogether if funding dries up. Baserow also looks good, but already appears to be open core and another single-vendor project. Undb might be a more community driven project over time.…
It's funny how people put funny names on the concept of a spreadsheet nowadays
I thought about some very trivial apps that are worth building but not worth the cost of the usual stacks. We are talking about the equivalent of a simple desktop app that doesn't need hosting except you don't want to use the local filesystem because you want to synchronize your data between devices. The actual app could be a simple SPA. It doesn't matter how it is implemented. What I am missing is the storage concept. There is remoteStorage.js but nobody adopted it.
I've been looking at and trying the class of easy to host, api-fied db/table frontend tools for a while. Clicking around your demo the sought-after functionality is there and the roadmap looks promising, good job! Some ui-breakpoints for a mobile view on tables are missing and not yet catalogued in the issue tracker. Use-case: string searching a table on the go.
It's funny how people put funny names on the concept of a spreadsheet nowadays
Earlier quoted context omitted.
GP didn't ask about references. They asked what the tool actually was, and asked about the types of guarantees it provides compared to a known RDBMS.
I got it. And in my opinion the most value undb provide is to handle the reference part which you always have to impl in code when you use traditional RDBMS. Also it provides typed api, real-time sub and user friendly views