Is your feature request related to a problem? Please describe.
Oracle lower/mixed case table names are not supported.
We've added test tables to demonstrate this.
- pso_data_validator."DvtCaseCamel"
- pso_data_validator."dvt_case_lower"
CamelCase appears to mostly work but fails in our custom raw metadata processing which is upper casing the name:
source = f'"{database}"."{table}"'.upper()
Lower casing is failing in Ibis code, root cause unknown.
Workarounds proposed to the customer:
- Create a view that converts problem identifiers to upper case.
- Use a custom query validation.
Because there are viable workarounds we might choose to not prioritise this feature request. We should certainly wait until after the upcoming Ibis upgrade to even think about this.
Search for tests skipped due to issue-1733 to reproduce these problems.
What version of DVT are you using?
8.x
What type of connections are you using for source and target?
Oracle
Is your feature request related to a problem? Please describe.
Oracle lower/mixed case table names are not supported.
We've added test tables to demonstrate this.
CamelCase appears to mostly work but fails in our custom raw metadata processing which is upper casing the name:
Lower casing is failing in Ibis code, root cause unknown.
Workarounds proposed to the customer:
Because there are viable workarounds we might choose to not prioritise this feature request. We should certainly wait until after the upcoming Ibis upgrade to even think about this.
Search for tests skipped due to issue-1733 to reproduce these problems.
What version of DVT are you using?
8.x
What type of connections are you using for source and target?
Oracle