rluech opened a new issue, #33029: URL: https://github.com/apache/superset/issues/33029
### Bug description [max_column_name_length](https://github.com/apache/superset/blob/master/superset/db_engine_specs/oracle.py#L30) is set to 30 in the OracleEngineSpec class. But since [Oracle Version 12.2 ](https://blogs.oracle.com/ebstech/post/upgrade-support-for-oracle-database-12102-and-11204) the [max field name length is 128](https://docs.oracle.com/en/database/oracle/oracle-data-access-components/19.3/odpnt/EFCoreIdentifier.html). Oracle Versions prior to 12.2 have reached end-of-life long ago. There is no direct configuration option or environment variable in Superset to override the max_column_name_length for Oracle, as far as I know. Can we set the default max_column_name_length = 128 with the next Superset release? The original Q&A: [33016](https://github.com/apache/superset/discussions/33016) ### Screenshots/recordings _No response_ ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### Browser Chrome ### Additional context _No response_ ### Checklist - [ ] I have searched Superset docs and Slack and didn't find a solution to my problem. - [ ] I have searched the GitHub issue tracker and didn't find a similar bug report. - [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
