Yet another web application.
yep. personally, prefer native apps for this use case, I wrapped duckdb into a nice native mac app: https://macdatapro.com
The DuckDB Local UI
181–190 of 197 posts
Re: The DuckDB Local UI
#182I do not know much about DuckDB but it sure looks awesome. Something I haven't found yet is a small swiss army knife for time series type of data: system and network monitoring, sensors and market data. I usually put everything in Prometheus but it is awkward. I would really love to find something I can query intuitively with SQL, have very basic plotting capability, read/parse some log files, can be queried without…
You might give QuestDB a try, it supports all the above except native graphing, though it does support Grafana and have a nice query UI. It's lightweight and blazing fast in my experience.
Thanks, it looks awesome !
Re: The DuckDB Local UI
#183Re: The DuckDB Local UI
#184I do not know much about DuckDB but it sure looks awesome. Something I haven't found yet is a small swiss army knife for time series type of data: system and network monitoring, sensors and market data. I usually put everything in Prometheus but it is awkward. I would really love to find something I can query intuitively with SQL, have very basic plotting capability, read/parse some log files, can be queried without…
Have a look at https://sql-workbench.com eventually. It runs DuckDB WASM in the browser, and with Perspective, which is used for data visualization, you can also visualize timeseries.
You can either drag & drop data, or use remote data sources via https
Re: The DuckDB Local UI
#185This looks pretty great. The UI looked fantastic, and the post mentioned that it was open source. However what's open source appears to be the DuckDB extension, which forwards the requests to a remote URL. I've not been able to find the code for the actual UI. Is the actual UI open source, or is that something MotherDuck is allowing to be used by this while remaining proprietary? Right now it doesn't appear like this…
So just to clarify, it's not really a local UI, ie I can't use it on an airgapped machine?
Re: The DuckDB Local UI
#186Anecdote. Last year I had to work with a heavy analytics process. The whole thing was 4 or 5 large steps and was written with PySpark. It was really slow and memory on my system run quite low (on a 8Gb system with a generous swap), sometimes even stopping the whole processing of the pipeline. For one heavy step we tried out DuckDB and I was blown away how performant against PySpark was. It was not only fast as hell b…
Spark is never going to be the right choice when running on a single system. Spark is for when you have a hundreds of machines worth of processing to do
Motherduck has an excellent article about this: https://motherduck.com/blog/the-simple-joys-of-scaling-up/
Re: The DuckDB Local UI
#187I love DuckDB Labs. They get to work on their cool engine. Get paid by Databricks to build Delta Support. Get paid by MotherDuck to build a UI. Always making the core open-source offering better, but getting massively VC funded companies to pay for it.
Actually, the UI was built by MotherDuck…
Re: The DuckDB Local UI
#188Weirdly, as cool as this looks, it's a bit concerning to me. It feels like this is marking a milestone in the history of a great open source project where they are doing one or many of the following: 1) Biting off more than they can chew, 2) Putting significant effort into something that's outside of their core value proposition, 3) Leaning more in the direction of supporting things with a for profit company that gra…
duckdb labs didn't make the UI, motherduck did. The extension just launches the web UI. you might have a point on #3, but they need to pay the bills somehow.
But they got a custom CLI argument in the OSS product for it. And hosting/proxying it under the OSS domain ui.duckdb.org
Re: The DuckDB Local UI
#189i’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.
After playing around for a while, a few things come to mind: * Being able to specify a db at startup would be pretty cool. I'm teaching a class on SQL this summer and I'm already envisioning workflows where a gatekeeper proxy spins up duckdb-ui containers on-demand for users as they log in/out, and it would be much better if the UI can be pre-seeded with an existing database. * This is maybe a big ask, but markdown c…
duckdb -ui pre_seeded_db.db
duckdb -ui -init startup.sql
Alternatively place statements/commands in `~/.duckdbrc` and just run `duckdb -iu`.
Re: The DuckDB Local UI
#190it would be awesome if these worked: duckdb -ui data.parquet duckdb -ui data.sqlite
duckdb -cmd 'CREATE TABLE my_data AS FROM READ_PARQUET($$data.parquet$$)' -ui
`duckdb -ui sqlitedb.db` should work bc duckdb can read sqlite files. If it doesn't autoload extension, you can INSTALL/LOAD in to your ~/.duckdbrc