On 10/20/08, Roy Lyseng <[EMAIL PROTECTED]> 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...
I agree with Roy on this one. The way Oracle works is that you can (actually, I believe you MUST) define a full path to each tablespace. I believe you should be able to do this for InnoDB tablespaces (whether file_per_table or not, one big kicker about file_per_table is that you can't specify more than one directory....) and for files related to MyISAM, CSV, etc. I don't know how a default datadir would be compatible with this, but I think having this stored in metadata is the right way to go -- IMO, the main reason people use symlinking is because they want to have the files on a different partition/disk that has more space. The only other reason I've seen used in practice is to standardize paths on a non-standard machine without restarting mysqld. Neither of those reasons are worth the pain caused by someone deleting files that they don't realize are symlinked, the security issues, and symlinking to NFS mounted directories, etc. -Sheeri
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
