Tom Ebergen

Hi @fisher-liquid, Thank you for filing the report. I took a look at this and I think this is expected behavior, it's just that the result size is extremely large....

TL;DR Ah yes, technically this isn't a cross product, sorry for the confusion. My explanation for why isn't great, but it has to do with correlated subqueries and the unnest...

Ok yea, so this is an issue with our Parser most likely. For some reason DuckDB detects a correlated subquery when in reality this is not a correlated subquery. It...

Thanks! Tagging https://github.com/duckdb/duckdb/issues/8859 since the two are similar issues

@cboettig Not sure, but potentially this PR will address your issue? https://github.com/duckdb/duckdb/pull/8475

pure SQL repo here, https://github.com/duckdb/duckdb-r/issues/72 @cboettig do you think you could make the dataset publicly accessible again?

Hi, I've been able to reproduce it. It seems to be a bug indeed. I'm working on narrowing down the exact issue, but a current workaround would be to 1....

Hmmm, I'm not positive, but there may be a difference in setting up a tempdir vs connecting to a persistent database file Can you try replacing the second line with...

Hi Simon, I think what you are seeing here is the effect of DuckDB materializing the data from the table, allocating the R data frame, then copying the data into...

Sorry, my mention of feedback wasn't clear. To clarify, feedback from DuckDB would be some kind of notification to the user that DuckDB requires more memory than what is specified...