On Wed, Oct 19, 2011 at 4:25 AM, Mark Atwood <[email protected]> wrote: > I was not a fan of LOCAL INFILE, and if it's still there, I think it should > come out. > If a DBA wants to load data without network delays, they would be better > served to ssh into the database machine and connect to localhost.
Careful: You might be mixing the meaning of LOCAL or without-LOCAL here. LOAD DATA INFILE = server reads CSV file from server filesystem. LOAD DATA LOCAL INFILE = file is on client filesystem, then sent to server. Arguably, the server-side function could be removed on same grounds as SELECT INTO OUTFILE. However, it would be nice to preserve the latter, client-side option. Like you say, that one could be used even on the server: ssh into the server and then do LOAD DATA LOCAL INFILE, now it's the client doing the work but there's no network. In practice the client-side implementation uses the same code server side (client just sends the file to server, then does LOAD DATA INFILE normally) so you can't then remove the code from the server either. Also note that similar security concerns do not apply here as they do for SELECT INTO OUTFILE. Summary: We should preserve one way of easily loading CSV data into a table. There is no reason, security or otherwise, why not to do so: either we should keep the current stuff or replace it with something new, don't remove it. henrik -- [email protected] +358-40-8211286 skype: henrik.ingo irc: hingo www.openlife.cc My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
