Hi Eric, all,

On Fri, Mar 19, 2010 at 9:23 PM, Eric Day <[email protected]> wrote:
>> from <catalog-name>.information_schema.<table-name>
>
> I'm not sure if this should be allowed or not (leaning towards
> no, does the standard say?). We may want to require always having a
> catalog context, and not allowing catalog in a fully-qualified table
> name. Of course in the protocol there is no way to specify a catalog

Standard says:

<schema name> ::= [ <catalog name> <period> ] <unqualified schema name>

> on connect (at least MySQL protocol), so we would need some default
> catalog depending on user. They could then SET CATALOG x like you
> show below (and this may be the only required auth check for catalog).

On authentication and default catalog, the standard says:

"
4.37.2 SQL-session identification
...
An SQL-session has a default catalog name that is used to effectively
qualify unqualified <schema name>sthat are contained in <preparable
statement>s when those statements are prepared in the current
SQL-session by either an <execute immediate statement> or a <prepare
statement> or are contained in <direct SQL statement>s when those
statements are invoked directly. The default catalog name is initially
set to an implementation-defined value but can subsequently be changed
by the successful execution of a <set catalog statement> or <setschema
statement>.
"

> Hopefully the abstractions in the environments where catalogs are
> used will make using them intuitive (ie, I have access to account or
> domain X, which maps to a catalog of the same name). For those folks
> who have no interest in dealing with catalogs, they should never see
> them or need to deal with setting them (get the default NULL catalog).

Yeah, that'd be great if you can solve it transparently. Perhaps I am
being under-appreciative of the merits of catalogs, but I don't see
the light yet.

kind regards,

Roland

>
> Best regards,
> -Eric
>



-- 
Roland Bouman
http://rpbouman.blogspot.com/

Author of "Pentaho Solutions: Business Intelligence and Data
Warehousing with Pentaho and MySQL",
http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470484322.html

_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help   : https://help.launchpad.net/ListHelp

Reply via email to