On Apr 21, 2011, at 8:58 PM, Stewart Smith wrote: > On Wed, 20 Apr 2011 07:33:18 -0700, Barry Leslie <[email protected]> > wrote: >> On 4/19/11 10:16 PM, "Stewart Smith" <[email protected]> wrote: >> >>> On Fri, 08 Apr 2011 09:00:42 -0700, Barry Leslie >>> <[email protected]> >>> wrote: >>>> I am using drizzled::getDataHomeCatalog() to find a home for my pbms >>>> database so I should be OK I think. >>> >>> getDataHomeCatalog() is going away, instead there being a catalog in >>> session to get the path from. >> >> OK. >> >> If I understand correctly the idea is that users do not have access across >> catalogs but is there anything like a 'system' catalog that is accessible to >> users in any catalog in which system information is available, possibly just >> read only? > > Once connected to a catalog, you cannot switch catalogs. Queries don't > span catalogs. > > there is the 'local' catalog which is the default (and existing > one). But if you connect to another catalog, you cannot access it. Each > catalog is it's own unique namespace.
Oh wow I didn't know that! That's pretty cool! Very nice to see catalogs making their way into Drizzle! Tim _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
