Copy to clipboard now only copies first 100 rows
I noticed as part of the UI improvements recently, that the "copy" button now only returns the first 100 rows (or whichever page of results you're currently viewing).
Being able to copy an entire table for quick pasting into Google Sheets was one of my favorite Mode features, as it saves the hassle of exporting to CSV, then importing into Sheets, then remembering to get rid of the CSV file cluttering your desktop. I never had an issue copying tables with thousands of rows.
Is the copy first 100 rows thing by design (if so, what problem is it solving)? If not, please restore the copy button functionality to copying the whole result set, thanks!
Hey Austin King , this is a change we made with the introduction of Helix, our new data engine powering Mode. Before Helix, all of the results from your SQL queries were downloaded to the browser, and that Copy button you're highlighting would then attempt to put whatever was in your browser onto the clipboard. (Sadly, we know it would often fail, too!)
Now, thanks to Helix, Mode Business and Enterprise customers can run queries that return up to tens of millions of rows, which we can't download to the browser all at once. The grid that displays your SQL query results currently loads in 100 records at a time; clicking that arrow to turn the page sends a request to Helix, asking for the next page of data.
We understand the value of being able to copy more than 100 records at a time and are now working on possible solutions that aren't constrained to whatever page of data you have in view in your SQL query results grid. Thanks for your feedback and patience as we work through this -- we'll keep you posted!Reply
Mike DeCarlo thanks for the explanation - I'm definitely noticing that things are running quite a bit snappier lately. I can imagine that the copy button would cause problems with massive datasets, but I've never encountered problems copying a table with up to a few thousand rows (nor would I want to copy something that huge).
Hopefully a workaround is identified soon, but in the meantime keep up the great work.Reply