Hi! > For shared hosting, the ACLs are trivial (although this requires a bit > of work): a simple yes/no permission on the whole database. Each > user has permission to their db.
I am not sure why you are saying this. I mean, if I am a customer and I would get a bunch of DBs from my hoster to create applications on, does that suddenly mean I don't want to be able to rigorously lock my application users out of the tables and columns that I definitely don't want them to accidentally access? Does it suddenly mean I don't want a readonly user that I know i can trust to run reports with? I think application based authorization has its purposes, and I would not want to say I want everything to be db based, but db-based authorization (and authentication) sure is a convenient feature. > or... just have a real schema/database/table hierarchy and users have > schemas. i.e. whole structure per user. What do you mean exactly? I don't recognize this hierarchy from other products. Just curious... regards, Roland > > This may play casual havoc with some engines :) > -- > Stewart Smith > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp > -- Roland Bouman http://rpbouman.blogspot.com/ _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
