GitHub user rluech edited a discussion: Why does sqlLab encypt long fieldnames?
We notice that when jumping from Chart to Run in SQL Lab, long fieldnames get hashed / encrypted (see printscreen attached). Is this a bug or a feature, and why? Is there a way to disable this encryption? https://github.com/apache/superset/blob/629b137bb00b87d6d7345cbae0b1b8d3dc439598/superset/db_engine_specs/base.py#L1973 `cls.max_column_name_length` `cls.force_column_alias_quotes` https://github.com/apache/superset/blob/master/superset/db_engine_specs/oracle.py#L30 > class OracleEngineSpec(BaseEngineSpec): engine = "oracle" engine_name = "Oracle" limit_method = LimitMethod.WRAP_SQL force_column_alias_quotes = True max_column_name_length = 30 Why is for Oracle `force_column_alias_quotes = True` and `max_column_name_length = 30` GitHub link: https://github.com/apache/superset/discussions/31997 ---- This is an automatically sent email for notifications@superset.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@superset.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
