-
Notifications
You must be signed in to change notification settings - Fork 92
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
show table rules #760
show table rules #760
Conversation
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #760 +/- ##
==========================================
+ Coverage 38.38% 40.33% +1.94%
==========================================
Files 254 265 +11
Lines 26359 26897 +538
==========================================
+ Hits 10119 10849 +730
+ Misses 15121 14881 -240
- Partials 1119 1167 +48
☔ View full report in Codecov by Sentry. |
proto.NewValueString(strings.Join(columns, ",")), | ||
proto.NewValueString(""), | ||
proto.NewValueString(fmt.Sprintf("%s", vs.Table.Computer)), | ||
proto.NewValueInt64(int64(step)), |
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.
How about changing step
to varchar
? I mean, for the columns [{"column":"foo"},{"column":"bar","step":2}]
, we can return:
... | columns | ... | steps |
---|---|---|---|
... | foo,bar | ... | 1,2 |
c8ec947
to
36093db
Compare
36093db
to
b365ceb
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
|
||
for _, v := range tests { | ||
rows, err := db.Query(v.sql) | ||
defer rows.Close() |
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.
Use closure instead, never defer
in a for-loop directly.
What this PR does:
support
show table rules from
Which issue(s) this PR fixes:
Fixes #628
Special notes for your reviewer:
Does this PR introduce a user-facing change?: