CTE inspection is amazing. I spend too much time doing that manually.
In datagrip you can select part of a query and execute it to see its result.
Instant SQL for results as you type in DuckDB UI
111–120 of 124 posts
Re: Instant SQL for results as you type in DuckDB UI
#112DuckDb 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…
Nothing comes close to the power of mongodb aggression pipelines.. when used in production apps it reduces the amount of code significantly for us by doing data modeling as close as possible to the source
[grizzled kdb+ user considers starting an argument but then thinks better of it]
Re: Instant SQL for results as you type in DuckDB UI
#113If there are any DuckDB engineers here, I just want you to know that your tool has been incredible for my work in bioinformatics/biotech. It has the flexibility/simplicity that biological data (messy, changing constantly) requires.
Re: Instant SQL for results as you type in DuckDB UI
#114It 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…
This is the stuff nightmares are made out of. Keep that style of coding out of any project I’m involved in, please.
What do you dislike about that style?
Re: Instant SQL for results as you type in DuckDB UI
#115Earlier quoted context omitted.
This is probably stupid, but at the hope of helping others through exposing my own ignorance -- I'm having trouble actually installing and running the preview... I've downloaded the preview release duckdb binary itself, then when I try to run "duckdb -ui", I'm getting this error: Extension Autoloading Error: An error occurred while trying to automatically install the required extension 'ui': Failed to download extens…
Sorry you hit that! This is actually already working on version 1.2.2. Could you install that version? That should get you going for the moment! We will dig into what you ran into.
All good, v1.2.2 works fine, thank you!
Re: Instant SQL for results as you type in DuckDB UI
#116Earlier quoted context omitted.
This is the stuff nightmares are made out of. Keep that style of coding out of any project I’m involved in, please.
What do you dislike about that style?
He/she isn't used to it. Any R, Elixir, or F# developer would be right at home with this syntax.
Re: Instant SQL for results as you type in DuckDB UI
#117There's something about this commercial company embracing this OSS project that I love that I very much don't love.
Re: Instant SQL for results as you type in DuckDB UI
#118Please finally add q language with proper integration to your tables so that our precious q-SQL is available there. Stop reinventing the wheel, let's at least catch up to the previous generation (in terms of convenience). Make the final step.
Maybe they're busy so it might be faster if you do it instead.
My intention is good. I advise right way. It's not an offense. (I have my job to do. They may consider doing what I say, it will be then their job to do)
Re: Instant SQL for results as you type in DuckDB UI
#119Earlier quoted context omitted.
An autocomplete that shows only the column names of the desired table BEFORE the from clause is typed by the user would require a time machine. Sure you can do something that is close enough, but the LINQ authors were looking for precision in the autocompletion and for the LINQ query to have the same ordering as expression syntax. The goals of this syntax are very precise and people seem to like it. Once again: calli…
So you want it to work this way, regardless of how well autocomplete works? Sounds like its about your personal comfort to make it work like another system you are more familiar with, which is exactly what I suggested. It doesn't require a time machine, just a basic understanding of statistics or probability.
I’m comfortable with pretty much anything. It took me like 2 mins to get used to this syntax in LINQ.
On the other hand, statistical autocomplete is not as good as having a precise autocomplete that does’t require jumping around lines.
My point here is that different people enjoy different things. There is no need to shit on other people’s accomplishments or preferences.