On Tue, Dec 16, 2008 at 10:09:30AM -0500, Jim Starkey wrote: > I think it would be appropriate if the drizzle server got out of the > business of dropping files on behalf of storage engines. It's > dangerous, saves a trivial amount of code, and violates the layering of > server on storage engine. The whole idea that a) users can control > database file names and b) the server stupidly deletes files by > extension wasn't a really clever idea on day one and hasn't got a whole > lot smarter since. > > If the philosophy is to defer to storage engines, then defer to storage > engines and stop trying to do them favors.
This is what's happenning in my discovery work. If you don't have any engine loaded that has a create_database call in it, we'll use the default handler which calls mkdir. 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... -- Stewart Smith _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
