@Marain .. you probably know this: http://dev.mysql.com/doc/refman/5.1/en/user-resources.html . This is same for MySQL and MariaDB.
I_S is a *read-only* database. And if you want to add more configurable per-user limitations such should IMHO go to the `mysql` database. I also don't think (for compability) that it should be more rows added `mysql`.`user` then, but maybe rather a new table specific for such patch ( `mysql`.`user_addon` or whatever). But what per-user limitations do you want to add exactly? Peter (from Webyog and thus not a MariaDB developer - just a follower here) On Mon, Jun 20, 2011 at 20:03, Marian Marinov <[email protected]> wrote: > Hello guys, > I have a lot of clients requesting some kind of per user limiting based on > the > information from the STATISTICS tables. > > I'm thinking of creating a patch that will add this functionality by > creating > two more tables in the INFORMATION_SCHEMA: > USER_LIMITS > CLIENT_LIMITS > > They will have some parts of the structure of USER_STATISTICS and > CLIENT_STATISTICS and will keep only values for limits. By default a 0 > would > mean no limit. > > Do you have any comments about my aproach? > > Would you be willing to accept a patch that adds such functionality? > > I want to know before I start work on this project if the community is > interested in such enhancement of MariaDB. > > Regards, > Marian > > _______________________________________________ > Mailing list: https://launchpad.net/~maria-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~maria-developers > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
