Feedback
Did this article resolve your question/issue?

   

Article

Connection.getMetadata().getTables() return incorrect results using Google Big Query JDBC driver 6.0

Information

 
TitleConnection.getMetadata().getTables() return incorrect results using Google Big Query JDBC driver 6.0
URL Nameconnection-getmetadata-gettables-return-incorrect-results-using-google-big-query-jdbc-driver
Article Number000121034
EnvironmentProduct: Progress DataDirect for JDBC for Google BigQuery Driver
Version : 6.0
OS: JAVA
Database : N/A
Application: All supported applications
Question/Problem Description

Created a JDBC connection to  Big Query instance using project P1 and dataset D1 initially.
Then  connection.getMetadata().getTables() and Connection.getMetadata().getColumns() returns the correct set of  tables and columns in the project P1 and dataset D1.
Then added some new tables into the project P1 and dataset D1.
Then those same two JDBC API calls returns the same set of results that was returned in the first call.
That means, the newly created tables in the same dataset were not returned in the result set.

Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
The map files, created during the connection time, was not updated with the newly created tables and columns.
Resolution
Setting the connection parameter CreateMap=forceNew resolved the problem.
Workaround
Notes
Last Modified Date11/6/2019 5:14 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.