Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.0.5
-
Fix Version/s: 10.0.8
-
Component/s: None
-
Labels:None
Description
As discussed on IRC, it should work as a normal GRANT <privilege>, but now it doesn't. The test case is below, cannot push it or record the result since it doesn't work.
--disable_warnings drop database if exists db; --enable_warnings --error 0,ER_CANNOT_USER drop role auto_create; create database db; create role auto_create; grant all on db.* to auto_create; --error 0,ER_CANNOT_USER drop user foo@localhost, bar@localhost; grant auto_create to foo@localhost; grant auto_create to bar@localhost identified by 'baz'; --connect (con1,localhost,foo,,db) set role 'auto_create'; create table t1 (i int); --disconnect con1 --connect (con1,localhost,bar,baz,db) set role auto_create; insert into t1 values (1); --disconnect con1 --connection default drop user foo@localhost, bar@localhost; set @sql_mode_saved = @@sql_mode; set sql_mode = 'no_auto_create_user'; --error ER_PASSWORD_NO_MATCH grant auto_create to foo@localhost; grant auto_create to bar@localhost identified by 'baz'; --error ER_ACCESS_DENIED_ERROR --connect (con1,localhost,foo,,db) --connect (con1,localhost,bar,baz,db) set role auto_create; drop table t1; --disconnect con1 --connection default drop user bar@localhost; drop role auto_create; drop database db; set sql_mode = @sql_mode_saved;
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Sorry about misspelling your name here. Phone autocomplete.
understand what exactly that means.
jira@mariadb.atlassian.net> wrote:
https://mariadb.atlassian.net/browse/MDEV-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
now it doesn't. The test case is below, cannot push it or record the result
since it doesn't work.
"stalled" is just a name of the state in a workflow, you can see a link "view workflow" next to the state. in short, it means that the issue was "in progress" and now it's not "in progress", but is not "closed" either.
But never mind that, I took your fix and pushed it into 10.0-serg tree, it will soon be in 10.0, then I'll close this issue. See above - I'm the assignee now, so you aren't expected to do anything for this issue anymore.
Hi Sergey!
I see that this issue is marked as stalled at the moment. I don't
understand what exactly that means.
Is there something else that needs to be done for this particular issue?
Vicentiu
On 14 Jan 2014 17:29, "Sergei Golubchik (JIRA)" <jira@mariadb.atlassian.net>