You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reproducible at least with an Oracle database, when using the "Connect using custom params" keyword and the python oracledb module. See #173 for an example of connection details.
Running such a keyword: Check If Exists In Database SELECT id FROM person WHERE first_name = 'Franz Allan';
leads to an error: DatabaseError: ORA-00933: unexpected token at or near ;
Removing the semicolon after the statement makes the keyword work without any errors. Check If Exists In Database SELECT id FROM person WHERE first_name = 'Franz Allan'
Even if it's somehow an expected error from the Oracle side (which I'm not sure about, need to check), I believe that the Database library should be tolerant enough to make such a simple command run properly.
The text was updated successfully, but these errors were encountered:
Fixed. The executed SQL statement will be now stripped before the execution - the trailing semicolon is removed.
Other databases seem to work OK if there is no semicolon in the end.
Reproducible at least with an Oracle database, when using the "Connect using custom params" keyword and the python oracledb module. See #173 for an example of connection details.
Running such a keyword:
Check If Exists In Database SELECT id FROM person WHERE first_name = 'Franz Allan';
leads to an error:
DatabaseError: ORA-00933: unexpected token at or near ;
Removing the semicolon after the statement makes the keyword work without any errors.
Check If Exists In Database SELECT id FROM person WHERE first_name = 'Franz Allan'
Even if it's somehow an expected error from the Oracle side (which I'm not sure about, need to check), I believe that the Database library should be tolerant enough to make such a simple command run properly.
The text was updated successfully, but these errors were encountered: