dbt2 test data, MySQL load data

[Jim Starkey]

It's getting time to see what ol' Nimbus can do.  The logical place to 
start was to load put the dbt2 data.  Boom.  A null value in the test 
data for a not null timestamp field.  So I checked against the MySQL 
test data:

    mysql>  select ol_delivery_d, ol_i_id, ol_dist_info
        -> from order_line
        -> where ol_o_id=2102
        -> and ol_d_id=1
        -> and ol_w_id=1
        -> and ol_number = 1;
    +---------------------+---------+--------------------------+
    | ol_delivery_d       | ol_i_id | ol_dist_info             |
    +---------------------+---------+--------------------------+
    | 0000-00-00 00:00:00 |   75216 | DyECOnPbxQryrmLlpIXZZJUJ |
    +---------------------+---------+--------------------------+
    1 row in set (0.00 sec)


That sure looks like a null (or invalid) timestamp to me.  The table 
definition is:

    ORDER_LINE="CREATE TABLE order_line (
      ol_o_id int(11) NOT NULL default '0',
      ol_d_id int(11) NOT NULL default '0',
      ol_w_id int(11) NOT NULL default '0',
      ol_number int(11) NOT NULL default '0',
      ol_i_id int(11) default NULL,
      ol_supply_w_id int(11) default NULL,
      ol_delivery_d timestamp NOT NULL,
      ol_quantity double default NULL,
      ol_amount double default NULL,
      ol_dist_info varchar(24) default NULL,
      PRIMARY KEY  (ol_w_id,ol_d_id,ol_o_id,ol_number)
    )"

The actual data from the load file is:

    column 1: 2102
    column 2: 1
    column 3: 1
    column 4: 1
    column 5: 75216
    column 6: 1
    column 7:
    column 8: 5
    column 9: 8134.160000
    column 10: DyECOnPbxQryrmLlpIXZZJUJ

This sure looks like a bug in LOAD DATA INFILE to me.

-- 
Jim Starkey
President, NimbusDB, Inc.
978 526-1376