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 complaining about various type mismatches with the data I'm
loading that I went in a fixed maunually using Excel but then it stopped
complaining tht I had bad data types after I made all the fixes and now it
just shows this error mesage when attempting to load the data into
the table:  ERROR 1329 (02000): No data - zero rows fetched, selected, or
processed

Ferindo

On 6/26/06, Dan Buettner <[EMAIL PROTECTED]> wrote:

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 data), I think it's much more likely
the command you're using isn't quite right for the data source you've got.

See http://dev.mysql.com/doc/refman/5.0/en/load-data.html for all the
ins and outs of LOAD DATA INFILE.

Off the top of my head, two things:

1 - you are using tab delimited data.  By default, I believe LOAD DATA
INFILE expects a comma delimited file.  You should therefore specify
FIELDS TERMINATED BY "\t"

2 - you are using Windows, which uses CRLF line endings.  I believe LOAD
DATA INFILE by default expects UNIX standard line endings.  You should
therefore specify LINES TERMINATED BY "\r\n"

Something like this then:

LOAD DATA INFILE 'C:/Program Files/Apache Software
Foundation/Tomcat 5.5/
webapps/utrad/docs/rebuild_scratch_area/test.tab'
INTO TABLE reggie
FIELDS TERMINATED BY "\t"
LINES TERMINATED BY "\r\n";


Hope this helps
Dan


Ferindo Middleton wrote:
> 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 of
the
> db so instead of giving a meaningful messgae, it just says: ERROR 1329
> (02000): No data - zero rows fetched, selected, or processed
>
> Ferindo
>
> On 6/23/06, Ferindo Middleton <[EMAIL PROTECTED]> wrote:
>>
>>  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 Software
>> Foundation/Tomcat 5.5/
>> webapps/utrad/docs/rebuild_scratch_area/test.tab' INTO TABLE reggie;
>>
>> The fields inside the file are tab-delimited and look like this:
>>
>> 16411 5 Rupert Settles Settles Settles 1 esunindyo \N 207 \N 12 \N
>> 2005-01-03 2005-01-07 1 1 1 0 \N Deobligation 1 2 \N fmiddleton 0 0 \N
>> \N 11:00:00 \N \N \N 0 0 4 0 0 \N \N \N 1
>>
>> The structure of the TABLE reggie is this:
>>
>> CREATE TABLE `reggie ` (
>>   `id` bigint(20) unsigned NOT NULL auto_increment,
>>   `title_salutation_id` bigint(20) unsigned NOT NULL,
>>   `firstname` varchar(128) NOT NULL,
>>   `middlename` varchar(128) NOT NULL default '',
>>   `lastname` varchar(128) NOT NULL default '',
>>   `suffix` varchar(128) NOT NULL default '',
>>   `paper_received` tinyint(1) NOT NULL default '1',
>>   `addr` text,
>>   `cc_email_list` text,
>>   `fortran_id` bigint(20) default NULL,
>>   `office` text,
>>   `class_id` bigint(20) unsigned NOT NULL,
>>   `schedule_id` bigint(20) default NULL,
>>   `start_date` date NOT NULL default '0000-00-00',
>>   `end_date` date NOT NULL default '0000-00-00',
>>   `enrolled` tinyint(1) default NULL,
>>   `attended` tinyint(1) default NULL,
>>   `completed` tinyint(1) default NULL,
>>   `cancelled` tinyint(1) default '0',
>>   `cancelled_comments` text,
>>   `comments` text,
>>   `email_confirmation_sent` tinyint(1) NOT NULL,
>>   `employment_status_id` bigint(20) unsigned NOT NULL default '0',
>>   `last_updated` timestamp NOT NULL default CURRENT_TIMESTAMP on update
>> CURRENT_TIMESTAMP,
>>   `last_user_updated` text,
>>   `waitlisted` tinyint(1) default '0',
>>   `overflow_registrant` tinyint(1) default '0',
>>   `attach_hotel_listing_directions` tinyint(1) default NULL,
>>   `instructor_legacy` text,
>>   `time_legacy` time default NULL,
>>   `ssn_legacy` text,
>>   `position_grade_title` text,
>>   `office_phone_legacy` text,
>>   `contractor_legacy` tinyint(1) default NULL,
>>   `no_show` tinyint(1) default NULL,
>>   `funding_id` bigint(20) unsigned NOT NULL default '0',
>>   `incomplete` tinyint(1) default NULL,
>>   `prerequisites_completed` tinyint(1) default NULL,
>>   `score` smallint(5) unsigned default NULL,
>>   `per_diem_cost` decimal(10,0) default NULL,
>>   `travel_cost` decimal(10,0) default NULL,
>>   `first_migration` tinyint(1) unsigned default NULL,
>>   PRIMARY KEY
>>
(`firstname`,`middlename`,`lastname`,`suffix`,`class_id`,`start_date`,`end_date`),
>>
>>   UNIQUE KEY `id` (`id`),
>>   KEY `fk_registration_class_id_must_always_match_a_classes_id`
>> (`class_id`),
>>   KEY `fk_registration_title_id_must_always_match_title_salutations_id`
>> (`title_salutation_id`),
>>   KEY `fk_registration_bureau_id_must_always_match_a_bureaus_id`
>> (`bureau_id`),
>>   KEY `fk_funding_id_check_for_registration_and_attendance`
>> (`funding_id`),
>>   KEY `fk_employment_status_id_check_for_registration_and_attendance`
>> (`employment_status_id`),
>>   CONSTRAINT
>> `fk_employment_status_id_check_for_registration_and_attendance`
>> FOREIGN KEY
>> (`employment_status_id`) REFERENCES `employment_statuses` (`id`),
>>   CONSTRAINT `fk_funding_id_check_for_registration_and_attendance`
>> FOREIGN
>> KEY (`funding_id`) REFERENCES `funding_types` (`id`),
>>   CONSTRAINT `fk_registration_bureau_id_must_always_match_a_bureaus_id`
>> FOREIGN KEY (`bureau_id`) REFERENCES `bureaus` (`id`),
>>   CONSTRAINT `fk_registration_class_id_must_always_match_a_classes_id`
>> FOREIGN KEY (`class_id`) REFERENCES `classes` (`id`),
>>   CONSTRAINT
>> `fk_registration_title_id_must_always_match_title_salutations_id`
FOREIGN
>> KEY (`title_salutation_id`) REFERENCES `title_salutations` (`id`)
>> ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
>>
>> Do you know why this this one data record won't load?... why MySQL
says:
>> ERROR 1329 (02000): No data - zero rows fetched, selected, or processed
>>
>> Ferindo
>>
>> On 6/23/06, Gerald L. Clark <[EMAIL PROTECTED]> wrote:
>> >
>> > 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 is wrong. Of course, I
>> > know
>> > > that
>> > > there is in fact data in the file and that it is proper data types
>> > matching
>> > > the table structure so I don't know why this error message is
>> occuring
>> > or
>> > > what it is about the file that's stopping it from being loaded.
>> > >
>> > Since you did not show us the data, nor the command you used to load
>> the
>> > data, we can't tell you what is wrong.
>> >
>> > --
>> > Gerald L. Clark
>> > Supplier Systems Corporation
>> >
>>
>>
>>
>> --
>> Ferindo Middleton
>> Technical Lead - Research and AUI Infrastructure Development
>> Sleekcollar Software
>>
>
>
>

--
Dan Buettner




--
Ferindo Middleton
Technical Lead - Research and AUI Infrastructure Development
Sleekcollar Software

Reply via email to