On 12/1/08, David Axmark <[EMAIL PROTECTED]> wrote: > > On Sun, 2008-11-30 at 19:51 -0500, Sheeri K. Cabral wrote: > > On 11/30/08, Brian Aker <[EMAIL PROTECTED]> wrote: > > > > Well, IMO, there are indeed good tools external to the > > database to do > > all this stuff. Exchanging data through a storage > > engine in this > > manner would merely be a convenience feature. > > > > Unless it was for performance? Loading data is something that > > is a low hanging fruit for us to do. Though in the end it is > > very dependent on the engine. > > > > 1) the only reason to keep LOAD DATA INFILE is performance. > > Otherwise, you can use batch insert commands. > > > Hmm, I would say that > > LOAD DATA INFILE 'file.txt' INTO TABLE t1 (@var1, @var2, col3) > SET col1 = LOWER(@var1), col2 = MD5(@var2); > > is convenient. And I think JimW did say the same thing. > > So it has another value compared to just speed. And when you can combine > ease of use with speed I think its a good thing. > > > /David > > > Convenient, but IMO not necessary in the core. ETL functionality is, to me, a plugin. Desirable, not required in the microkernel.
-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
