Hi Stewart A few weeks ago you were finishing the catalogs and we discussed on IRC how one should actually end up in ones own confined catalog. (different tcp/ip port per catalog were mentioned as one way)
I just wanted to come and say I think for many cloud-like use cases the username is the best key. The counterargument to this was that at least with some auth_ plugins, especially the mysql-like auth_schema, the users would be stored inside the catalog, so we have a chicken egg problem. But upon thinking it seems one could simply require users to pass the catalog name prepended to the username and dot as separator. This would also allow to have identically named users in different catalogs, which is clearly desired. Examples: drizzle --host=shared.host --user=mycatalog.hingo --password=sshhh myschema On server side I should know be connected to mycatalog, after which the "mycatalog." is stripped from the username. Internal to the catalog I would still be known as hingo. Note that if dots are disallowed in catalog names, also the following is perfectly fine: drizzle --host=shared.host --user=mycatalog.henrik.ingo --password=sshhh myschema Also note that if someone else wants to create a catalog called "hingo" or a username called "mycatalog", that is also fine, as they would then connect to it as: drizzle --host=shared.host --user=hingo.otheruser --password=sshhh otherschema and drizzle --host=shared.host --user=othercatalog.mycatalog --password=sshhh otherschema I vote that this should be the common way of using catalogs. henrik -- [email protected] +358-40-8211286 skype: henrik.ingo irc: hingo www.openlife.cc My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
