distal-attribute
distal-attribute
distal-attribute
distal-attribute

Cannot import CSV

User, date Message
Written by leekaiwei
8 months ago
Category: Import/Export
3 posts since Sun, 12 Jan 14
I am using Windows 8.1 64-bit, MySQL 5.6.15, HeidiSQL 8.2.4690 and I'm trying to import a CSV file but it is failing with the error below.



I have successfully imported this file using Sequel Pro on a Mac OSX machine, with Western (Windows Latin 1) encoding, which I assume the below is the equivalent of.



This is the table setup.



A typical line of the CSV is

http://gyazo.com/8ebcb5530fb3a90d0b3daea0d50d9c37



What is happening?
Written by leekaiwei
8 months ago
3 posts since Sun, 12 Jan 14
Ok, well I managed to mess up my first post pretty badly and I can't see an edit button. What is meant to be in the first post:




AB1 0AA,57.101478,-2.242852,385386,801193,NJ853011,"","Aberdeen City","Lower Deeside Ward", S12000033,S13002484,Scotland,S99999999,"Aberdeen South",1980-01-01,1996-06-01,"","",,,"","",""

Written by BubikolRamios
8 months ago
327 posts since Thu, 14 Jan 10
Heidi sql does have some issuses with files format & encoding.
First try with 'client parses file content' option.

But in any case check manualy if all rows were imported, even if all goes witout any error !

Check also if '(' in file path is doing problems.
Written by leekaiwei
6 months ago
3 posts since Sun, 12 Jan 14

BubikolRamios wrote: Heidi sql does have some issuses with files format & encoding.
First try with 'client parses file content' option.

But in any case check manualy if all rows were imported, even if all goes witout any error !

Check also if '(' in file path is doing problems.



Sorry for late reply but thanks for the help. I moved the file to a different location so it didn't have the '(' and it worked perfectly.
Written by ansgar
6 months ago
4988 posts since Fri, 07 Apr 06
'(' and ')' in the filename are not your problem. It's the "escape" control character, which must not be the same character as the "field encloser". You have selected " for both, but the LOAD command needs different chars here to work properly.

There is no file encoding problem here, and HeidiSQL does not have "some issues" with encodings, or at least very few. In this case the servers LOAD command is the one to blame.
 

Please login to leave a reply, or register at first.