Correct query exception details and fixes for "Script As" requests #514
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes two issues introduced by recent refactoring:
Batch queries that raised an exception while executing were masking the initial db exception and throwing a custom error, which was displayed to the user. This has been resolved to allow the original db error to be displayed by updating the expected types for resultSetSummaries.
Scripting requests were not having their parameters correctly deserialized and as a result, object property accessors were being called on a
dict
. TheObjectMetadata
attribute type forscripting_object
originally had a hacky deserialization workaround because the client/server contracts were misaligned for making a script request. When that was removed for typing fixes, theparameter was no longer getting deserialized into the correct type, and was left a
dict
.I also removed some debugpy configuration that was preventing attaching to the process for breakpoint debugging.