agusfigueroa-htg commented on issue #18085: URL: https://github.com/apache/superset/issues/18085#issuecomment-1018411477
Hi all, First of all thanks for the discussion. It's very enriching, and the proposed solution would reach case consistency and solve the issue as mentioned. After sharing this with our team another option that popped up, **in case this only affects filters interoperability**, is to add the option to make the filters case insensitive. In that case, instead of looking for columns named the same (`dataset1.colname=dataset2.colname`), we can apply the filters "case insensitive" like (`lower(dataset1.colname)=lower(dataset2.colname)`), creating a flag for it in case users want to apply it or not. This would lay fully on the Superset side and would be transparent across different databases and what they decide to do in the future (return uppercase, lowercase, mix case or so). -- 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
