-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HammerDB CLI issue with Changing MsSQLs ODBC Driver #118
Comments
Hi, yes confirmed as a bug. It is checking if the driver has been changed by matching "*driver" and then picking this up for this particular variable that clashes. A fix will be added to the next version. As a workaround you can run the following instead and set the value directly (it is advisable to drag the command window out a big larger so the line does not overlap when typing).
The setting of the driver value in tpcc itself is not affected as the string match works correctly here so it is only the mismatch that needs fixing.
|
Fix for Issue #118 using diset with variables with spaces
Hello, Im seeing this same error when I use the web service to try and set the driver. I'm on HammerDB version 4.7. |
The REST interface was deprecated following the discussion in this issue #420 because of lack of use. |
When trying to replicate the GUI workflow I have used on the CLI, when I try to change the driver in the connection setting, with the command:
diset connection mssqls_odbc_driver {ODBC Driver 17 for SQL Server}
I get the following error:
Clearing Script, reload script to activate new setting
Script cleared
Error: Driver script must be either "test" or "timed"
I noticed this is same error given when I try to change the value in the "tpcc" part of the dict that is similar: "mssqls_driver".
I think the problem might be that the variable checking logic from the tpcc driver item might be crossed with the connection part of the dict.
Thanks
The text was updated successfully, but these errors were encountered: