Roy Lyseng wrote:
Brian Aker wrote:
Hi!
Historically folks have been able to control the directory of
datafiles and indexfiles for MyISAM. They have also been able to
"symlink" file around in the directories. Now this has opened up a
can of worms in the past, but the security issues around it have not
come up in recent time.
Seeing how modern disks are configured is this something we should be
supporting in the future? Does it still make sense?
I am leaning toward "no" but it would be nice to hear from deployment
folks if this matters.
IMHO, forcing the database(schema)/directory relationship is the
bigger problem. With tablespaces there would be no need for symlinks.
Not coming from the deployment space, though...
This begs the large and more difficult question of the relationship
between databases, schemas, and tablespaces. What is a database? What
is a schema? MySQL defines "database" and "schema" as synonyms. Since
most people seem to agree that while a tablespace is contained within a
single database, a schema (necessarily, for performance) can be spread
among a number of tablespaces presumably on different drives. Having
schemas and databases be the same object rather complicates it.
MySQL resolved the issue with a typically Ronstromian Dictat of "the
rule is that there are no rules", leaving it to individual storage
engines to manage the namespace and semantics of whatever a tablespace
might be, leading the situation where the storage engine name is an
explicit part of a tablespace identifier.
But perhaps drizzle has already re-architected a cow out of this hambuger...
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
