From: Johan De Meersman Date: January 31 2012 9:52am Subject: Re: Converting Microsoft SQL database to MySQL List-Archive: http://lists.mysql.com/mysql/226706 Message-Id: <1fadc299-01ac-435f-a20a-aa662934df72@zimbra> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable ----- Original Message ----- > From: "Hal=C3=A1sz S=C3=A1ndor" > > noting that MySQL does not really support CSV: one can set all Not *entirely* accurate: MySQL does include a CSV engine that you can use i= n the same way you would use InnoDB or any other engine. If you create a table a with engine=3DCSV and then go look at the data dict= ionary, you'll find the files a.frm and a.CSV there. You can then swap a.CSV out for a properly formatted CSV file with the same= structure as the table you've created; and if a select on the table then y= ields the data you were expecting, you can just do alter table a engine=3DI= nnoDB to magically transform it into a proper table. The other way around works, too, btw - you can easily do "create table expo= rt engine=3DCSV as select * from table" and then copy the resulting export.= CSV. Given that that functionality is there, though, it baffles me why a proper = CSV import/export mechanism has never been implemented. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel