The .import cmd has a problem when it encounters binary zeros embedded in data.
I have a large tab-separated text file which has some garbage (aka binary zeros) in one of the fields of one of the records. The .import cmd trips on this and terminates with this msg: /u/crdceed/data/RTM_NY_ceed_positionsPB.dat line 951: expected 14 columns of data but found 19 I should think this would be considered a bug. jim -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
