Skip to content
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

V2.0 Release #222

Merged
merged 14 commits into from
Oct 1, 2024
Merged

V2.0 Release #222

merged 14 commits into from
Oct 1, 2024

Conversation

amochin
Copy link
Collaborator

@amochin amochin commented Oct 1, 2024

No description provided.

amochin and others added 14 commits August 12, 2024 16:33
… 5.0.1 (#215)

* Keyword 'Check Row Count' using assertion engine

* Deprecate old "row count" assertion keywords

* Link to Assertion Engine in docs

* Deprecate duplicating "check exists" assertion keywords

* Log returned number of rows for possible debugging purposes

* Put Assertion Engine to dependencies

* Require min. Python 3.8 and RF 5.0.1

* improve common docs

* New keyword 'Check Query Result'

* Typo in docs
…uery Result' (#216)

* Retry mechanism for assertion keywords 'Check Row Count' and 'Check Query Result' (fix #209)

* Log message if timeout reached
* Log query results as a table (fix #147)

* Formatting

* Consistent naming of internal functions
… a dedicated keyword 'Set Logging Query Results' (#218)
Calling a stored procedure in MSSQL - special handling of OUT params
The entire connection logic and implementation was refactored

* There is only one mandatory parameter left - dbapiModuleName, it must be set - either as keyword argument or in config file.
* All other parameters are optional now. So if some connection data was missing, the error would come not from the Database Library, but from the Python DB module.
* If some params are not provided, they are not set to None - they are just not passed to the Python DB module at all.
* Other custom params from keyword arguments and config file are passed to the Python DB module as provided
* All parameters can be now set in a config file - including any custom params
* If same custom parameter is provided both as a keyword argument and in config file, the keyword argument value takes precedence.

Other changes

* Deprecate the Connect To Database Using Custom Params Keyword - it's not needed anymore, the updated Connect To Database keyword replaces it fully
* Stop using localhost as fallback value for DB host
* Stop using {SQL Server} as fallback value for pyodbc driver
* Update docs for the Connect To Database keyword, move docs for using the config file in a separate section
* Pythonic naming for keyword arguments (fix Use Python convention naming #188)
* Shorter / more precise names for some parameters
* Big cleanup of all docs
… set empty, allow custom params in connection string (similar to pyodbc), "TCPIP" is no default protocol value anymore
@amochin amochin merged commit d4ba70a into master Oct 1, 2024
20 checks passed
@amochin amochin deleted the dev branch October 2, 2024 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant