It's not the output formatting that is what is attractive, it's that in combination with the ability to be selective about which rows are returned. And to be able to join against other tables to make CSV report files to be delivered to someone is a powerful feature that can be done in a single statement. I think this is used for such reporting pretty commonly (though I have no actual numbers to back it up) and it would be a shame for us to lose such functionality, or to have to resort to a more complex solution where the logic is all moved out to a script.
All I'm saying is that it is a useful feature. Be sure all aspects of how it is used is considered before eliminating functionality. -Dave On Oct 19, 2011, at 2:31 PM, Olaf van der Spek wrote: > On Wed, Oct 19, 2011 at 8:24 PM, David Shrewsbury > <shrewsbury.d...@gmail.com> wrote: >> I've had occasions, in previous jobs, where being able to use >> INTO OUTFILE has saved a tremendous amount of time and >> pain. Not only can you specify the format of the output (field >> separators, etc), but you can also selectively retrieve only >> certain rows (rather than the entire table) by using a WHERE >> clause. Any replacement should offer the same type of >> functionality IMHO. > > Isn't that kind of output formatting easily handled by the scripting > language of your choice? > > Olaf _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
