On Fri, Jun 28, 2013 at 10:56:08PM +0300, to...@acm.org scratched on the wall: > Trying to import data into a table the operation stops on first error > (actually a rollback seems to be performed) because of column number > mismatch. > > Why does it not follow the .BAIL ON/OFF setting? And, why rows before > the error are removed? > > So, in .BAIL OFF mode, I expected errors to display, but the rest of > the file to be processed. Actually, this a very nice way to filter > somewhat a file from unwanted, badly formatted lines. (Now, the only > option seems to be manual editing of the text file for each error line, > and try again.) > > Is this operation by design or a bug?
By design. The .bail configuration applies to processing SQL batch files, not data imports. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
