Stewart,
this is a good question. Some comments below to start off a discussion...
Different engines have very different requirements for management of
tablespaces, so I think it is important that tablespaces are managed
entirely by the engine on the micro-level. Yet, on a higher level, it is
important that users can manage tablespaces through Drizzle commands
that generalize the management as much as possible.
How is this achievable?
- Create, modify and drop tablespace commands supported by Drizzle.
- Engine-specific parameters to tablespace commands
- Engine-specific namespace of tablespaces simplifies management.
- Tablespace configuration data can be managed by the engine or by the
server, interfaces for both can be provided.
- In the simplest case, the server stores all config data (XML, blob?)
and provides them to the engine when the server initiates the engine.
In the case of a distributed engine, it is much easier to keep
tablespace information consistent by managing config data in the engine,
in particular when multiple servers attach to the same engine.
BTW, HADB (a distributed server/engine) does not have tablespaces (or
rather it has a single unnamed tablespace). However, each server node is
given a list of file names on startup, and the concatenated storage
space provided by these files is used as storage space for that node.
Information about schemas and tables and mapping to which nodes they are
stored in is entirely through system-managed tables (the data dictionary).
Thanks,
Roy
Stewart Smith wrote:
On Mon, Oct 20, 2008 at 10:06:59AM +0200, Roy Lyseng wrote:
IMHO, forcing the database(schema)/directory relationship is the bigger
problem. With tablespaces there would be no need for symlinks.
You also have to think about where this information is being stored. How
will drizzle know where to look for tablespaces?
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
