Skip to content

Releases: microsoft/sqltoolsservice

v1.2.0-alpha.28

25 Oct 19:35
Compare
Choose a tag to compare
v1.2.0-alpha.28 Pre-release
Pre-release
Add rowcount check so that no results error is sent for a query where…

v1.2.0-alpha.27

25 Oct 10:27
Compare
Choose a tag to compare
v1.2.0-alpha.27 Pre-release
Pre-release
change return type from always true (#516)

v1.2.0-alpha.26: Port changes from master

22 Oct 21:33
Compare
Choose a tag to compare
fixed failing integration tests (#512)

* fixed failing integration tests

* close connection after test

* undo close connection

v1.2.0-alpha.25: Fix numerous Azure property issues (#511)

20 Oct 05:40
Compare
Choose a tag to compare
* Avoid crashing if azure edition is System.

* Add new Azure-specific options to the prototype and return through the service calls

* Send azure properties over database info request

* IsCloud should include Azure SQL DW
- Fixed references to this feature flag
- Updated edition handling to include ManagedInstance and removed AzureV1 check since it's never used and it's been retired.

v1.2.0-alpha.24: updated smo nuget package with latest bits (#508)

20 Oct 01:31
Compare
Choose a tag to compare
* updated smo nuget package with latest bits

* added new nupkg

* fixed peek definition test

* fixed batch parser wrapper tests

v1.2.0-alpha.23: Fix tools service crash + improve server edition naming (#506)

19 Oct 18:11
Compare
Choose a tag to compare
* Fix https://github.com/Microsoft/vscode-mssql/issues/986 and add better server edition naming
- Fixed a number of issues related to the binding queue, specifically the fact that it didn't capture exceptions that occurred on the binding thread. This caused the thread to crash the service.
  - The root cause of the error was when you get a connection error during init of the SmoMetadataProvider which threw an exception. Because of this no Binder was created, and the code would null ref later during processing
  - Added logic to handle null ref issue and other related code
  - Added a unit test for the new error handling path, and supported still returning some value in this case
- Separately, have a fix for an issue where the edition is shown as "SQL Azure" for all Azure connections. Fixing to be "Azure SQL DB" for this case and handle when the database reports as DW or Stretch instead. This maps better to users concept of what the edition should be and avoids returning what is an outdated term.

* Messed up the test - fixing this by returning the expected return object

v1.2.0-alpha.22

19 Oct 10:26
Compare
Choose a tag to compare
v1.2.0-alpha.22 Pre-release
Pre-release
added change database handler (#505)

v1.2.0-alpha.21: fixed the issue with parsing a windows path was failing in mac (#503)

18 Oct 19:30
Compare
Choose a tag to compare
* fixed the issue with parsing a windows path was failing in mac

v1.2.0-alpha.20

17 Oct 03:34
Compare
Choose a tag to compare
v1.2.0-alpha.20 Pre-release
Pre-release
update filebrowser expand contract and methods (#500)

v1.2.0-alpha.19: Improve error message handling (#497)

14 Oct 10:26
Compare
Choose a tag to compare
- Add special handling for token expired errors so they send with a clear flag that'll allow clients to take action on this case
- Send error message instead of callstack for all messages, and ensure all resource manager paths send back inner exceptions so users can understand the true root cause.