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

fix(query-interface): reject with error for describeTable #10528

merged 1 commit into from
Mar 9, 2019


Copy link

Pull Request check-list

Please make sure to review and check all of these items:

  • Does npm run test or npm run test-DIALECT pass with this change (including linting)?
  • Does the description below contain a link to an existing issue (Closes #[issue]) or a description of the issue you are solving?
  • Have you added new tests to prevent regressions?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
  • Did you follow the commit message conventions explained in

Description of change

Fixes #10513

Copy link

codecov bot commented Mar 9, 2019

Codecov Report

Merging #10528 into master will increase coverage by 0.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #10528      +/-   ##
+ Coverage   96.14%   96.16%   +0.01%     
  Files          92       92              
  Lines        9504     9508       +4     
+ Hits         9138     9143       +5     
+ Misses        366      365       -1
Impacted Files Coverage Δ
lib/query-interface.js 92.21% <100%> (+0.32%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 454cf48...30ebeb4. Read the comment docs.

@sushantdhiman sushantdhiman merged commit 7ccbb1e into master Mar 9, 2019
@sushantdhiman sushantdhiman deleted the describe-reject-error branch March 9, 2019 08:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

1 participant