Quarry always ordered the results sorted based on the first column ascending. That is not ideal; a lot of the time I explicitly put an "ORDER BY" clause in my query, but the result Quarry shows me in the end is ordered based on first column, not based on what I put in the ORDER BY clause.

Quarry should NOT order the results when it first loads them. The user can click on the columns to order them if they desire so.

Note that this only affects the HTML table that Quarry shows; if you download the data in CSV/JSON/TSV the downloaded file is ordered as specified in the SQL query (the correct way).