junlincc edited a comment on pull request #13210: URL: https://github.com/apache/superset/pull/13210#issuecomment-785228920
Additional to https://github.com/apache/superset/pull/13210#discussion_r582080120 on whether we should keep `SELECT` 1. SELECT has limitation in realizing complex hierarchy/grouping interaction. dimension/columns, metrics grouping and hierarchy are very common BI tool which which we currently lack. 2. When there are multiple DROP targets, dnd help set some drop restrictions. For example, If target A is dropped, target B will not accept drop values. (There are cases in PivotTable where groupby and column restrict each other) 3. performance. do we need to render options in dimensions/columns and metrics twice with both? @villebro @kgabryje @ktmud @mistercrunch let's keep the discussion going so Design can have enough information to go on. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
