Remix.run Logo
ltbarcly3 a day ago

This is such a bizarre feature.

thenaturalist a day ago | parent | next [-]

On first glance possibly, on second glance not at all.

First, repeat data analyst queries are a usage driver in SQL DBs. Think iterating the code and executing again.

Another huge factor in the same vein is running dev pipelines with limited data to validate a change works when modelling complex data.

This is currently a FE feature, but underneath lies effective caching.

The underlying tech is driving down usage cost which is a big thing for data practitioners.

hamilton a day ago | parent | prev [-]

What about it is bizarre?

pixl97 a day ago | parent [-]

It's probably different for duckdb, but from something like Microsoft SQL tossing off these random queries at a database of any size could have some weird performance impacts. For example statistics on columns you don't want them on, unindexed queries with slow performance, temp tables being dumped out to disk, etc.

hamilton a day ago | parent [-]

I agree; one thing that is neat about Instant SQL is for many reasons, you can't do this with in any other DBMS. You really need DuckDB's specific architecture and ergonomics.