The implicit LIMIT 1001 is there to avoid browsers being frozen on a huge HTML table, but - sometimes - browser slowness is a reasonable tradeoff for looking at large result sets.
Similarly, it's sometimes useful to be able to "paginate" the results via ie. LIMIT 1000 OFFSET 3000, which isn't currently possible.
So, try to account for it somehow, ie.
- in the javascript, check if the query contains
LIMIT (surrounded by spaces) and if it does, don't add the implicit LIMIT 1001
- this can however backfire; if the user matches against a literal string with
LIMIT in it, they get the FULL unlimited result set
- have a checkbox that says
LIMIT 1001 below the query, which would NOT be url-encoded
- everyone would have to un-tick it themselves, explicitly saying "I want unlimited results even if it freezes my browser"
- loses the convenience to link specific results to another person
- ???
The implicit
LIMIT 1001is there to avoid browsers being frozen on a huge HTML table, but - sometimes - browser slowness is a reasonable tradeoff for looking at large result sets.Similarly, it's sometimes useful to be able to "paginate" the results via ie.
LIMIT 1000 OFFSET 3000, which isn't currently possible.So, try to account for it somehow, ie.
LIMIT(surrounded by spaces) and if it does, don't add the implicitLIMIT 1001LIMITin it, they get the FULL unlimited result setLIMIT 1001below the query, which would NOT be url-encoded