giftig opened a new pull request, #25855:
URL: https://github.com/apache/superset/pull/25855

   ### SUMMARY
   <!--- Describe the change below, including rationale and design decisions -->
   
   Previously, this was a constant of powers of ten from 10 to 100000 and then 
we tacked on maxRow on the end, being the SQL_MAX_ROW config. This 
unfortunately results is very confusing behaviour if SQL_MAX_ROW is less than 
100,000 as it still let you select 100,000, though wouldn't acctually use that 
LIMIT, and the messaging would not acknowledge the setting for SQL_MAX_ROW 
either.
   
   Instead, construct the list by ascending through powers of ten until we 
reach the configured SQL_MAX_ROW.
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   <!--- Skip this if not applicable -->
   
![BEFORE-static](https://github.com/apache/superset/assets/2862039/64df2d87-0282-44c9-a9d3-7a94cb28e4be)
   
![AFTER-dynamic](https://github.com/apache/superset/assets/2862039/e28b06f7-2db9-4225-a215-088a31dc7fc5)
   
   ### TESTING INSTRUCTIONS
   <!--- Required! What steps can be taken to manually verify the changes? -->
   
   1. Set `SQL_MAX_ROW` to a value less than 100,000 or greater than 1,000,000
   2. Use the LIMIT dropdown in SQL Lab
   3. Observe that the drop down no longer displays values higher than 
`SQL_MAX_ROW`, and will display every power of 10 up to `SQL_MAX_ROW`
   
   ### ADDITIONAL INFORMATION
   <!--- Check any relevant boxes with "x" -->
   <!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [x] Changes UI
   - [ ] Includes DB Migration (follow approval process in 
[SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to