-
Notifications
You must be signed in to change notification settings - Fork 31
1.3.1 seems to hide syntax errors #54
Comments
I think that the difference in error message may be due to the difference in version of JDBC driver.
Please let me know the table definition and the query where the error occurred. Thanks, |
Gosh - that was fast! It looks like not the JDBC driver change: I'm running this SQL:
Our wrapper didn't support lists (now fixed) so app_list was a string rather than list object which caused the SQL error. On PyAthenaJDBC v1.1.1 (AthenaJDBC v1.0.1):
On PyAthenaJDBC v1.3.1 (AthenaJDBC v1.1.0):
Now trying with the alternative JDBC drivers: On PyAthenaJDBC v1.1.1 (AthenaJDBC v1.1.0):
On PyAthenaJDBC v1.3.1 (AthenaJDBC v1.0.1):
|
Thank you for the quick reply. I think that the implementation before change is somewhat dirty. I will think about the smart implementation by hand over the error information on the weekend. |
The execution environment is Python 3.6. |
Sorry for the late reply. Well, it has not changed much from the previous implementation 😂 |
super - that works well here - saves a load of time figuring out what's wrong :-) |
Running a (broken) query on v1.1.1:
However with v1.3.1 those really handy details seem lost:
I think this is the change that changed this:
c253586
I've tried to workaround this by putting that logic in my code but it looks like the data is lost (presumably as the exception is reraised)
The text was updated successfully, but these errors were encountered: