-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Column type name metadata incorrect for no schema binding views #89
Comments
Thanks @YotillaAntoni for submitting this issue! I'll take a look and get back to you when I have an update |
Any updates on this? |
Also seeing an issue where an |
@bhvkshah sorry for pinging you directy on this one. Is there any way you can fix this? our customers are having issues in Metabase due to this matter |
Driver version
2.1.0.14
Redshift version
PostgreSQL 8.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3), Redshift 1.0.49087
Client Operating System
macOS 13.3.1
JAVA/JVM version
OpenJDK Runtime Environment Temurin-11.0.17+8 (build 11.0.17+8)
Table schema
Problem description
Using
DatabaseMetaData#getColumns
method over the VIEWproduct_view_nsb
reports incorrect results for theTYPE_NAME
. It reportscharacter varying(100)
instead ofvarchar
for the columnproduct_name
, andnumeric(10,2)
instead ofnumeric
for the columnnet_price
Using the
DatabaseMetaData#getColumns
method over both TABLEproduct_table
or the viewproduct_view
returns the correct values,varchar
for columnproduct_name
andnumeric
for the columnnet_price
Expected behaviour:
The column
TYPE_NAME
for the describedproduct_view_nsb
view isvarchar
for columnproduct_name
andnumeric
for columnnet_price
Actual behaviour:
The column
TYPE_NAME
for the describedproduct_view_nsb
view ischaracter varying(100)
for columnproduct_name
andnumeric(10,2)
for columnnet_price
Any other details that can be helpful:
Looks like the error is in the last part of the query to get the metadata from
pg_get_late_binding_view_cols
, when it usescolumntype
asTYPE_NAME
instead ofcolumntype_rep
JDBC trace logs
log_nsb_view.log
Reproduction code
The text was updated successfully, but these errors were encountered: