From: Johan De Meersman Date: March 27 2012 10:33am Subject: Re: big character constant List-Archive: http://lists.mysql.com/mysql/227045 Message-Id: <99a14d5f-8b81-4a83-8bab-3c4423ac491b@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" > > input for Word (yes, I have to work MySQL CSV-ish output into real > CSV, ensuring that there are no escapes in it, nor 'NULL' either). And this is why it's beneficial to specify your goal along with your questi= on :-) MySQL does have a proper CSV engine; and it's mystifying why it isnt' acces= sible in any other way. I say "engine", and you can take that literally: ju= st like you have MyISAM and InnoDB engines, CSV is also an engine that is a= pplicable to tables. Just do a "create table myexport engine=3DCSV as select * from mytable;" an= d a myexport.CSV file will magically appear in the data directory. You'll n= eed the proper privileges to read it, of course; and you should use "drop t= able myexport;" to delete it instead of doing so from the file manager; but= it will be proper CSV. Note that CSV means "comma separated value", but that MS Excel, for one, te= nds to use semicolons instead. Shouldn't be a major hurdle in importing, th= ough. /johan -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel