Details
Description
When creating a view (be it regular or tabular) in the Goldfish UI, one currently has to run a query to get to the "save as view" step. If you have a ton of data, you will probably want to run the query with a LIMIT n option for some value of n for testing/validation - but want to save an unLIMITed version of the query as the view body (i.e., as the defining query). (Otherwise this approach won't scale to real database sizes.)
Ways to solve this might be to allow the view query to be edited during the save process, or looking for a LIMIT clause and asking whether to remove it, or even changing the UI to include an explicit LIMIT box (with a default value, e.g., 100, showing) and having the UI always add that LIMIT to the user's query unless they uncheck it and not adding it to the query when it's being incorporated in a view body. (The last approach is nicely more general, also addressing the recurring problem where customers naively run queries with giant results and wonder why it's taking so long as the browser tries to swallow them.)