81–90 of 124 posts
Earlier quoted context omitted.
It is already available in the local DuckDB UI! Let us know what you think! -Customer software engineer at MotherDuck
Does local DuckDB UI work without an internet connection?
It doesn't currently - the UI assets are loaded at runtime - but we do have an offline mode planned. See https://github.com/duckdb/duckdb-ui/issues/62.
DuckDb is missing a killer feature by not having a pipe syntax like kusto or google's pipe query syntax. Why is it a killer feature? First of all, LLMs complete text from left to right. That alone is a killer feature. But for us meatboxes with less compute power, pipe syntax allow (much better) code completion. Pipe syntax is delightful to work with and makes going back to SQL a real bummer moment (please insert meme…
DuckDb is missing a killer feature by not having a pipe syntax like kusto or google's pipe query syntax. Why is it a killer feature? First of all, LLMs complete text from left to right. That alone is a killer feature. But for us meatboxes with less compute power, pipe syntax allow (much better) code completion. Pipe syntax is delightful to work with and makes going back to SQL a real bummer moment (please insert meme…
Earlier quoted context omitted.
Curious if there has been any thought given to open sourcing the UI? Of course there's no obligation to though!
We do have plans. It's a question of effort, not business / philosophy.
Good to know a totally offline tool is being considered.
Thanks for the great tool BTW.
It would be even better if SQL had pipe syntax. SQL is amazing, but its ordering isn’t intuitive, and only CTEs provide a reliable way to preview intermediate results. With pipes, each step could clearly show intermediate outputs. Example: FROM orders |> WHERE order_date >= '2024-01-01' |> AGGREGATE SUM(order_amount) AS total_spent GROUP BY customer_id |> WHERE total_spent > 1000 |> INNER JOIN customers USING(custome…
The PRQL[1] syntax is built around pipelines and works pretty well. I added a similar "get results as you type" feature to the SQLite integration in the Logfile Navigator (lnav)[2]. When entering PRQL queries, the preview will show the results for the current and previous stages of the pipeline. When you move the cursor around, the previews update accordingly. I was waiting years for something like PRQL to implement…
I really like duckdb's notebooks for exploration and this feature makes them even more awesome, but the fact that I can't share, export or commit them into a git repo feels extremely limiting. It's neat-ish that it dodfoods and store them in a duckdb database. It even seems to stores historical versions, but I can't really do anything with it..
DuckDb is missing a killer feature by not having a pipe syntax like kusto or google's pipe query syntax. Why is it a killer feature? First of all, LLMs complete text from left to right. That alone is a killer feature. But for us meatboxes with less compute power, pipe syntax allow (much better) code completion. Pipe syntax is delightful to work with and makes going back to SQL a real bummer moment (please insert meme…
There’s an extension for that https://github.com/ywelsch/duckdb-psql
In DuckDB UI and MotherDuck. Awesome video of feature: https://youtu.be/aFDUlyeMBc8 Disclaimer: I’m a co-founder at MotherDuck.
Extension Autoloading Error: An error occurred while trying to automatically install the required extension 'ui': Failed to download extension "ui" at URL "http://extensions.duckdb.org/0069af20ab/osx_arm64/ui.duckdb_..." (HTTP 403) Extension "ui" is an existing extension.
Is it looking to download the preview version of the extension, but getting blocked/unauthorized (hence the 403 forbidden response)? Or is there something about the auto-loading behavior that I'm supposed to disable maybe?
Earlier quoted context omitted.
Maybe in the next version they could also implement support for DROP, with autocorrect for the nearest (not yet dropped) table name.
LLM powered queries that run in Agent mode so it can answer questions of your data before you know what to ask.