Our team is working with Redshift and utilizing SUPER fields that contain JSON-like objects. To effectively query and access these fields, we need to set the enable_case_sensitive_identifier parameter to true at the cluster or connection level. Unfortunately, queries involving case-sensitive identifiers fail when this parameter is not set.
We're wondering if there's a way to configure this setting within Metabase in a installation or query level or if there's a recommended workaround to achieve case-sensitive querying for SUPER fields.
do you mean "Additional JDBC connection string options"? I don't think it can work because according to the documentation RedShift doesn't support this flag in the connection string
What i mean is to set enable_case_sensitive_identifier at Redshift level not at connection level so every connection should by default have this as true