On Fri, Mar 19, 2010 at 04:05:03PM -0500, Tim Soderstrom wrote: > Ah ok. So basically you will be able to specify which database (and/or > catalog) someone can access but that's basically an all access backstage pass > to the DB (ie no allowing reads but not writes, etc.)?
That's currently how it works, but having some level of ACL (read/write) will probably be the next step. Basically, whatever is practical and doesn't hurt performance significantly. -Eric > On Mar 19, 2010, at 3:32 PM, Eric Day wrote: > > > Most things around authentication and authorization were removed early > > on, but pluggable authentication was added back in shortly after (PAM > > and HTTP plugins). Monty Taylor recently added in an authorization > > plugin point to restrict what schemas, tables, and processes a user > > can access. We're still thinking about simple ACLs like read/write, > > but not a full-blown grant system like traditional RDBM's have. > > > > The other main differences is that these user/account settings will > > most likely not be managed through the database plugins. Drizzle will > > only read this information from the plugin source. > > > > -Eric _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
