You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using SQLAlchemy Inspector in Oracle connector we face a problem with case sensitivity/insensitivity
If we check Oracle case insensitive table/schema/column names, they all will be uppercase
SQLAlchemy sees all them lowercased
To Reproduce
The bug we found:
In Oracle we have two tables with same name except for case (Oracle allows us to do so):
But if we see them in OpenMetadata:
They have completely similar structure and (probably) changed casing.
Expected behavior
We expect table/column/schema names to be shown as they are in source system (Oracle).
Version:
OS: Ubuntu Linux/Kubernetes
Python version: 3.9
OpenMetadata version: 1.3.2-1.4.8
Additional context
The problem was described here: #15471 (comment)
The text was updated successfully, but these errors were encountered:
problems with links to the tables of the foreign keys
Ex. we have a table 'A' which has a key to the table 'B'. When I trying to go to the table 'B' by clicking on the link on the frame 'Table Constraints' I get an error "table instance for ... not found". I realized that this is due to the fact that the table name on the frame is in lowercase letters ('b'), while the table itself is in uppercase.
Affected module
Oracle connector (backend)
Describe the bug
When using SQLAlchemy Inspector in Oracle connector we face a problem with case sensitivity/insensitivity
If we check Oracle case insensitive table/schema/column names, they all will be uppercase
SQLAlchemy sees all them lowercased
To Reproduce
The bug we found:
In Oracle we have two tables with same name except for case (Oracle allows us to do so):
But if we see them in OpenMetadata:
They have completely similar structure and (probably) changed casing.
Expected behavior
We expect table/column/schema names to be shown as they are in source system (Oracle).
Version:
Additional context
The problem was described here:
#15471 (comment)
The text was updated successfully, but these errors were encountered: