-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Adds non-conflicting default new database name #13099 #13103
Conversation
c4c4c8b
to
7bad0d6
Compare
Codecov Report
@@ Coverage Diff @@
## master #13103 +/- ##
=======================================
Coverage 54.36% 54.36%
=======================================
Files 465 465
Lines 69685 69685
=======================================
Hits 37881 37881
Misses 31804 31804 Continue to review full report at Codecov.
|
Nice work, but I think a better solution is to remove the default value entirely. |
Note also that we have #13104 which catches the situation where a user does enter the same database name, so we'll try continue having your pull request address the default values. |
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.
I'd also prefer not to have default value. Imagine user has databases named db1...db1000, with this patch going to operations tab would lead to 1000 queries just to have default value which almost nobody will use....
Do you also feel default value must be removed for rename form? |
Yes, I think having the field empty by default is best approach. |
7a703cb
to
4ca8cfb
Compare
Signed-off-by: Raghuram Vadapalli<raghuram.vadapalli@research.iiit.ac.in>
Merged as 553d1ff into QA_4_7 branch, thanks for your contribution! |
Signed-off-by: Raghuram Vadapalliraghuram.vadapalli@research.iiit.ac.in
Before submitting pull request, please check that every commit: