Single command expected

Friday, 5 April 2024 · 3 messages · last reply 8 Apr 2024
ВВ
Ветошкин Владимир5 Apr 2024 10:36 #
Hi, How can I kill session and then user:grant or user:drop permissions in a single command? When I make it in two different commands - user logins between them and the second command gets error, that the user is currently logged in.
-- С уважением, Ветошкин Владимир Владимирович
CG
Christian Grün8 Apr 2024 11:12 #
Hi Vladimir, There’s currently no such function available. Even if we had a user:kill function, we could not ensure that a user logs in a millisecond later when user:drop is going to be executed. We could enrich user:drop et al. with an “enforce” option to kill users, but the challenge is that a user may currently execute a long-running update query that needs to be finalized before the user can be dropped, thus delaying the execution of the user:drop operation and possible other subsequent requests. Have you already observed the presented pattern? Best, Christian
Quoted text · Ветошкин Владимир · 14 lines
On Fri, Apr 5, 2024 at 10:36 AM Ветошкин Владимир <en-trance at yandex.ru> wrote: > Hi, > > How can I kill session and then user:grant or user:drop permissions in a > single command? > When I make it in two different commands - user logins between them and > the second command gets error, that the user is currently logged in. > > -- > С уважением, > Ветошкин Владимир Владимирович > >
ВВ
Ветошкин Владимир8 Apr 2024 13:12 #
Hi, Christian, Thank you for your answer. I don't need to drop the user, but only user permissions. For now I have made the authorization deny function before user:kill. Then I change need user params, and then the authorization allow function is called. Hope this helps.
Quoted text · Christian Grün · 23 lines
08.04.2024, 12:12, "Christian Grün" <christian.gruen at gmail.com>: > Hi Vladimir, > > There’s currently no such function available. Even if we had a user:kill function, we could not ensure that a user logs in a millisecond later when user:drop is going to be executed. We could enrich user:drop et al. with an “enforce” option to kill users, but the challenge is that a user may currently execute a long-running update query that needs to be finalized before the user can be dropped, thus delaying the execution of the user:drop operation and possible other subsequent requests. > > Have you already observed the presented pattern? > > Best, > Christian > > > On Fri, Apr 5, 2024 at 10:36 AM Ветошкин Владимир <en-trance at yandex.ru> wrote: > > > Hi, > > > > How can I kill session and then user:grant or user:drop permissions in a single command? > > When I make it in two different commands - user logins between them and the second command gets error, that the user is currently logged in. > > > > -- > > С уважением, > > Ветошкин Владимир Владимирович > > >
-- С уважением, Ветошкин Владимир Владимирович

⚡Generated with XQuery