Stewart Smith wrote:
> On Wed, Dec 17, 2008 at 06:16:40PM -0500, Jim Starkey wrote:
>
>> Tim Soderstrom wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On Dec 16, 2008, at 6:22 PM, Stewart Smith wrote:
>>>
>>>> But at some point "soon", CREATE DATABASE will *not* map to mkdir.
>>>>
>>>> possibly we should even move to having each engine have a subdir in
>>>> datadir for their own stuff so as to not get in the way of each other...
>>>>
>>> +1
>>>
>>> I definitely agree that databases should be decoupled from
>>> directories, and that engines should have places to put stuff. I
>>> logged a feature request bug for MySQL (41306) on this issue in case
>>> anyone wants to se my crazy hair-brained ideas about that :) I think
>>> having an engine have it's own subdir (say $datadir/engines/$engine)
>>> is almost more important even. Otherwise, $datadir is just going to
>>> get trashed with all sorts of random files; or it will become more
>>> confusing to have to track which files go to which engine that could
>>> live anywhere on the file-system.
>>>
>>>
>> That is an excellent idea! Is it too late for MySQL 6.0?
>>
>
> For falcon you could have a falcon directory in datadir (as PBXT does)
> but this will show up in SHOW DATABASES as there's no way of setting
> anything to be ignored (and even then, it'll still pollute the namespace).
>
>
The Falcon unit of storage isn't the database (aka schema) but
tablespace. Since the purpose of tablespace is to put different tables
on different devices, it is orthogonal to database/schema.
Now, all that said, I wish each engine had a directory under the datadir
to avoid cross engine confusion. I regret that it is probably too late
to introduce this now.
While I don't expect to ever have a Nimbus storage engine for drizzle
(though a lot of other things I thought equally unlikely have happened),
Nimbus would have no foot print on the MySQL server disk whatsoever.
Ponder that!
--
Jim Starkey
President, NimbusDB, Inc.
978 526-1376
