This repository has been archived by the owner on Jan 28, 2021. It is now read-only.
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.
Add support for VIEWs in SHOW TABLES statements #862
base: feature/views
Are you sure you want to change the base?
Add support for VIEWs in SHOW TABLES statements #862
Changes from 8 commits
02c010c
fc97414
f6ff425
889bd1e
38bf07f
cb3b61c
9b8ecfa
1220b98
0329486
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Personally I think
if len(newItem) != 1 || len(newItem) != 2
would be clearer (also maybe a few nanoseconds faster, or not, depending on how Go optimizes).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, why do you think it is clearer? I see the interval (1,2) in the other case much more clear. But I guess that it only comes down to personal opinions. Although it would be cool to actually measure which one is faster!