More information in errors for native sql statements
Errors in native sql statements like in _execute always result in the same "Invalid SQL statement" error without any further information, which makes it really difficult to debug. More data - for example the part of the SQL statement that is invalid - would be really helpful! Especially as this error also seems to be thrown when the SQL is perfectly fine but a wrong _execute syntax is used, which should not throw an "Invalid SQL statement" error, as it is not about SQL!
[Deleted User]
shared this idea
-
Check Google Cloud Logging (Logs Explorer) for your Data Connect service in your Google Cloud console. Details of the backend SQL errors are logged in Cloud Logging. For security reasons, these are no exposed via the SDK APIs.
We have also shared a more detailed response on Stackoverflow : https://stackoverflow.com/a/79929034/233965.
PTAL and let us know if you need additional help.
