-
Notifications
You must be signed in to change notification settings - Fork 686
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
sql: add FLUSH PRIVILEGES hint #835
Conversation
May I request you make it clearer:
|
That's exactly what didn't work for me. Maybe it runs automatically, but not immediately? Context: https://github.com/photoprism/photoprism/blob/develop/internal/tidb/init.go |
If you are absolutely sure and it counts as a bug if it doesn't work immediately, I'll invest more time to debug the issue with unit tests 👍 |
Should execute |
This is also what your CTO told me. IMHO the docs should mention that, independent of what future releases might do. Does running |
Yes, I worked on this code recently: pingcap/tidb#8886 When you run This is MySQL compatible behavior.
Yes it can be an expensive command if there is a large number of users. |
Ah, fixed 5 days ago? No wonder it doesn't work for me. What about users that run older versions? |
I fixed it for the case of the test suite 5 days ago, if you have etcd, the notification channel should still work. If it doesn't, that is a new bug.
The docs are internally versioned (although currently the website only shows 'master' - that is something that is being worked on). /cc @queenypingcap |
We use the local version for our software. I know, special use case. We are a test suite for new ideas. |
Also it seems there are ready-to-use Docker images out there, that use the local version. These people will waste a lot of time figuring out what's wrong, like I did. At least half a day. |
Do you mean tidb w/mocktikv (no tikv or pd)? If so, that was my motivation for fixing that bug :-) As well as this one pingcap/tidb#8836. I would love to chat more if you don't mind me emailing you.
If it is documented as it is though, that means it is intended behavior. It is not intended, or MySQL compatible. We could change the wording and apply to non-master docs, or we could backport the fix to existing GA releases. I am fine with either approach. |
I had a chat with @shenli. I will prepare a patch to backport to the 2.1 branch. |
A backport to 2.1 is now pending review pingcap/tidb#8948 |
Sounds good! Let's have a chat, here are my contact details: https://blog.liquidbytes.net/contact/ |
Changes LGTM. Thanks for editing! |
sql/user-account-management.md
Outdated
|
||
## Flush privileges | ||
|
||
If you modified the grant tables directly, please run the following command to apply changes immediately: |
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.
If you modified the grant tables directly, please run the following command to apply changes immediately: | |
If you modified the grant tables directly, run the following command to apply changes immediately: |
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.
We usually do not use "please" in technical documents.
sql/user-account-management.md
Outdated
FLUSH PRIVILEGES; | ||
``` | ||
|
||
See [Privilege Management](privilege.md) for details. |
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.
See [Privilege Management](privilege.md) for details. | |
For details, see [Privilege Management](../sql/privilege.md). |
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.
Is ../sql/
a mistake? Both documents are in sql, so ../sql is the same directory.
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.
@lastzero No, ../sql/
is not a mistake. Your link path is correct on GitHub, but on the PingCAP website it will be a broken link.
Our link rule: Any relative path that links to another file must start from the level of the root directory.
We updated the link path rule for SEO. Thanks for your cooperation :)
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.
Interesting. You use pandoc, right? In my own projects, MkDocs automatically creates the right links in HTML as needed.
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.
@lastzero We do use pandoc to convert HTML to PDF, but it has nothing to do with our links in the documents.
We have our own link rule because of the complex hierarchical relationship in our website.
@lastzero Thanks for your contribution! |
Co-Authored-By: lastzero <michael@lastzero.net>
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.
LGTM
It looked like FLUSH PRIVILEGES is not implemented because of pingcap/tidb#674. user-account-management.md also didn't mention it. I've added to all relevant pages.