Well that's good to know. This is a InnoDB engine db. I did try specifying
the how the fields and lines in the file are terminated to the LOAD DATA
INFILE program but I still get the same error message.
Still have no idea what I'm doing wrong. I was getting errors where the
program was
Does MySQL have any constraints when it comes to the number columns that it
can accurately support/import in any one table/file. When I see this file
that is failing to get properly read into the database, that's what comes to
mind... It's failing because of some kind of constraint or threshold
Ferindo -
I believe there is a 64K limit on the length of a record in a MyISAM
table (text and binary columns excluded), but I haven't ever seen a
number of columns limit. Based on your table description below I don't
think you're close to such a problem.
Based on the error you receive (no
I'm trying to load data into a table from a file but I get an error message:
ERROR 1329 (02000): No data - zero rows fetched, selected, or processed
This error message isn't very specific as to what is going wrong and I have
no idea what it is about the data file that is wrong. Of course, I
Ferindo Middleton wrote:
I'm trying to load data into a table from a file but I get an error
message:
ERROR 1329 (02000): No data - zero rows fetched, selected, or processed
This error message isn't very specific as to what is going wrong and I have
no idea what it is about the data file that
I guess my general reason for posting this was to ask: Are there any known
issues with the LOAD DATA INFILE comand in MySQL? However, I stripped all
the data in the file (test.tab) down to one record which still wouldn't
load. Here is the command:
mysql LOAD DATA INFILE 'C:/Program Files/Apache
