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

bindinfo: set default db for bindings correctly #14077

Merged
merged 3 commits into from
Dec 27, 2019

Conversation

alivxxx
Copy link
Contributor

@alivxxx alivxxx commented Dec 16, 2019

What problem does this PR solve?

For bindings like select * from test.t, it should be used in every db, not only the db that created it.

What is changed and how it works?

For sqls that have no implicit databases, we set the default db to empty, so it can be used regardless of current db.

Check List

Tests

  • Unit test

Code changes

  • Has exported function/method change

Side effects

  • None

Related changes

  • None

Release note

  • None

@alivxxx alivxxx added the type/enhancement The issue or PR belongs to an enhancement. label Dec 16, 2019
@alivxxx alivxxx requested a review from a team as a code owner December 16, 2019 10:39
@ghost ghost removed their request for review December 16, 2019 10:39
@codecov
Copy link

codecov bot commented Dec 16, 2019

Codecov Report

❗ No coverage uploaded for pull request base (master@09a7a21). Click here to learn what that means.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master     #14077   +/-   ##
===========================================
  Coverage          ?   80.1799%           
===========================================
  Files             ?        482           
  Lines             ?     120953           
  Branches          ?          0           
===========================================
  Hits              ?      96980           
  Misses            ?      16237           
  Partials          ?       7736

Copy link
Member

@winoros winoros left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@alivxxx alivxxx added the status/LGT1 Indicates that a PR has LGTM 1. label Dec 18, 2019
Copy link
Contributor

@eurekaka eurekaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@eurekaka eurekaka added status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Dec 27, 2019
@sre-bot
Copy link
Contributor

sre-bot commented Dec 27, 2019

/run-all-tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants