We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
running a stored procedure or insert statement triggers this error.
The text was updated successfully, but these errors were encountered:
a59b464
chore(release): 1.2.0 [skip ci]
31ab363
# [1.2.0](v1.1.0...v1.2.0) (2022-04-14) ### Bug Fixes * **non utf chars from sftp:** removed non-utf chars from files downloaded over sftp ([d6dc334](d6dc334)), closes [#105](#105) * **parallel runs:** fixed project run all execution ([46b00ca](46b00ca)), closes [#75](#75) * **saml auth:** fixed bugs with saml login process ([d68a6f0](d68a6f0)), closes [#122](#122) ### Features * **mssql:** mssql queries with no output should not crash, insert, delete statements ([a59b464](a59b464)), closes [#72](#72) * **sql timeout:** added sql timeout option to connection and query run ([1e174ac](1e174ac)), closes [#75](#75)
🎉 This issue has been resolved in version 1.2.0 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀
Sorry, something went wrong.
No branches or pull requests
running a stored procedure or insert statement triggers this error.
https://stackoverflow.com/questions/16561362/how-to-check-if-a-result-set-is-empty
The text was updated successfully, but these errors were encountered: