Live data from Hacker News

The DuckDB Local UI

duckdb.org

101–110 of 197 posts

Re: The DuckDB Local UI

#101

Earlier quoted context omitted.

The online demo looks great and promising, too bad it's unusable for me. I've tried installing it with conda from conda-forge and no luck. I've tried installing it with pip, the same. I've also cloned the repository from github, tried to build it and failed, but I don't remember the details. Why is some software so difficult to install beats me.

Have you ever reported an issue? I use perspective heavily on a variety of platforms both conda and pypi without any problems.

Not yet, because I wanted to give it one more try while documenting all the steps.

Re: The DuckDB Local UI

#103

Earlier quoted context omitted.

I'm a bit out of the loop here, but what's the use case for DuckDB?

DuckDB is mind blowingly awesome. It is like SQLite, lightweight, embeddable, serverless, in-memory database, but it's optimized to be columnar (analytics optimized). It can work with files that are in filesystem, S3 etc without copying (it just looks at the necessary regions in the file) by just doing `select * from 's3://....something.parquet'`. It support automatic compression and automatic indexing. It can read j…

I'm sorry, I must be exceptionally stupid (or haven't seriously worked in this particular problem domain and thus lacking awareness), but I still can't figure out the use cases from this feature list.

What sort of thing should I be working on, to think "oh, maybe I want this DuckDB thing here to do this for me?"

I guess I don't really get the "that you want to learn something about" bit.

Re: The DuckDB Local UI

#104
post #73

Earlier quoted context omitted.

https://github.com/denoland/denokv You can self host Deno KV since over a year.

That doesn't change what they're saying. The self-hosted backend you're linking is a network-accessible version of the local SQLite backend. The hosted backend is transparently globally replicated and built on FoundationDB, with a very different (better) scaling story.

Given the floss implementation, if one wanted, they could create their own DenoKV backed by anything they like... Azure Cosmos, DynamoDB, CockroachLabs are all possible, and given the relatively small API, should be relatively easy to do if anyone wanted to do such a thing.

Re: The DuckDB Local UI

#105

This looks great! At risk of harping on a tired topic, have you thought about embedding an AI query generator? For ad-hoc queries like I mostly use DuckDB for I’ve found it’s almost always fastest for me to paste the schema to ChatGPT, tell it what I’ll looking for, then paste the response back into the DuckD CLI, but the whole process isn’t very ergonomic. I think I’m sort of after duckbook.ai, but with access to a…

The UI of duckbook.ai is great! I wish someone would open-source something similar!

Re: The DuckDB Local UI

#106
post #51

Earlier quoted context omitted.

Reminiscent of what Deno are doing with their Deno K/V feature, which works in the open source project using SQLite but gets a big upgrade if you use it with Deno Deploy: https://til.simonwillison.net/deno/deno-kv I'm OK with this. Commercial open source projects need a business model. I get why this can be controversial, but the ecosystem needs to find ways to fund future development and I'm willing to compromise on…

I think primary concern is will DucDb pull something like RedisLabs. Wherein they are open source till it gets enough traction and after that pull the rug.

To be fair, the “traction” here was AWS using their massive competitive levers to kill RedisLabs’ long-existing (and quite reasonable/tolerated by open source) monetization avenue, risking the continued funding for redis.

To characterize this as a rug pull is unfair IMO.

Re: The DuckDB Local UI

#107

The UI looks nice and is by itself a welcome addition. I am somewhat at odds with it being a default extension build into DuckDB release. This still is a feature/product coming from another company than the makers of DuckDB [1], though they did announce a partnership with makers of this UI [2]. Whilst DuckDB has so far thrived without VC money, MotherDuck has (at least) 100M in VC [3]. I guess I'm wondering where the…

I think this is a bit of a non issue. The UI is just that, a UI. Take it or leave it. If it makes your life easier, great. If not, nothing changes about how you use DuckDB.

There is always going to be some overlap between open source contributions and commercial interests but unless a real problem emerges like core features getting locked behind paywalls there is no real cause for concern. If that happens then sure let’s talk about it and raise the issue in a public forum. But for now it is just a nice convenience feature that some people (like me) will find useful.

Re: The DuckDB Local UI

#108
I don't have anything to say in regards to DuckDB or this UI. But, I do find it funny that their homepage animation causes google to index the description as:

DuckDB is a fast ana| database system.

Re: The DuckDB Local UI

#109
post #3

i’m one of the co-founders at MotherDuck. our team is building the UI in collaboration with the team at DuckDB Labs. this is a first release. we know there are going to be tons of feature requests (including @antman’s request for simple charts). feel free to chime in on this thread and we’ll keep an eye on it! meanwhile, hope you enjoy this release! we had lots of fun building it.

> The DuckDB UI is also fully open source: visit the duckdb/duckdb-ui repository if you want to dive in deeper. Is this really the case? The repo doesn’t seem to have any ui elements?

We updated the video [if that's the reference], because it is not yet open source. Thanks for pointing that out!
Post reply on HN