Hi!
On Dec 18, 2008, at 3:38 PM, Jim Winstead wrote:
On Thu, Dec 18, 2008 at 3:06 PM, Jim Starkey <[email protected]>
wrote:
and don't forget that there's this thing called a catalog that some
databases support, and in fact some of the mysql connectors equate
database and catalog, not database and schema.
Should we support catalogs? I've been going back and forth about this.
At the moment they really are not supported... the work to do them was
never merged into 5.0. They are just reserved for the future.
Multi-tenancy is the issue for me. Should a user(s) be given a
catalog? Should we just restrict this to schema? Should joins work
across them?
Is a catalog a simple namespace issue?
If we can get Innodb to stop doing a few things globally we could
allow one server to have multiple Innodb instances internally... every
catalog could have its own (as an example).
drizzle could avoid the horrible slowness of information_schema, and
In the current roadmap is to rework I_S so the are not materialized
(and use the same execution path as the engine).
some of the impedance mismatches between what is available from the
server and what the standard apis expect to have available.
What else are you thinking of?
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
