cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Choose Language Hide Translation Bar
View Original Published Thread


Fix JMP Bug: ODBC-Error not forwarded to user

What inspired this wish list request?  We have been struggling with incomplete datasets, i.e. from different query executions we got different number of rows from database using "new sql query" with ODBC-DSN. This occurs because the query connection runs in timeout during data fetch, and JMP did not forward the error and inform user about this.

 

What is the improvement you would like to see?  I need JMP to inform user about the ODBC error, that the user knows that there is an issue and she/he can fix it.

 

Why is this idea important?  Because with this behaviour the user looses the confidence that data acquisition by JMP works correctly and dataset is incomplete. It is just a bug fix. 

 

As a workaround I was told to configure the timeout in the ODBC-settings, but this will work only, when user is aware of the issue. Without JMP informing him about the issue, he will probably not be aware of it. Even when he is aware of the issue, the next query can take longer, and he again may run into the same issue. So he needs to pull the data several times to know if there is an issue. That's something that I don't like.

 

 

4 Comments
ArneTheSecond
Level I

Would be very helpful to get information of incomplete data sets.

DatabaseWhimp
Level I

Can you please also share here how to configure the timeout in the ODBC-settings?

Georg
Level VII

Dear @DatabaseWhimp ,

there are different ways, and it depends on your system/driver.

On Windows you can configure the setting in the DSN (windows app ODBC-Database-Administrator 64 bit), then go to user DSN and edit Connection settings.

See Screenshot, this will work for user DSN only, not for system DSN (that we have in our case, our IT has rolled out the DSN as system DSN).

Georg_0-1739528939552.png

 

Another way is to add a string to the end of the SQL you send to database in "Custom SQL()", with the connection settings, like here in this select:

select now() from dual()
CONTEXT('QUERYTIMEOUT' = '900')

Sarah-Sylvestre
Staff
Status changed to: Acknowledged

Thank you for sharing your request! We appreciate your input and will review it promptly. We'll keep you posted if there are any updates.