Fix result set rows for DDL queries to be null, instead of empty array #26
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.
The result set for DDL queries (INSERT, UPDATE, DELETE etc.) is empty,
i.e. it does not contain any columns or rows. Columns and rows should
thus be represented by a null value. In contrast, an empty result set
from a SELECT query will always contain a non-empty array of columns and
may contain any number of rows (possibly an empty array of rows).
Builds on top of #20