On 31/01/2009 8:20 AM, Mike Eggleston wrote:
> Wait. I ran the sqlite3 under script during lunch. I have the same
> behavior. The script also captured the first line of output from killing
> sqlite3. The output shows binary characters in an INSERT statement. The
> bad line is (characters coverted):
>
> (oops deleted the line, a few ^P, ^G, and ^0 characters)
> (found another)
> INSERT INTO File VALUES
> (3555,55862,1093685304,1817326624,1799833888,1092633120,'A A Bey BAA Y BGmuHb
> BFi8Ob BGfR','I A A C^V+I2SKHGKJVuCfW9BcGPWLQ\0\0^C\0g^A
> ø~^~G§\0^G;^C\0~J\0\0\0ã\r\0\05Ú\0\09P0A 4Rj IGk B A A A');
>
> In vi I finally used :g/[^A-^Z]/d to remove all binary characters.
>
> After removing that line I was able to load the entire file without
> errors. Thanks for the help.
Earlier question:
> Have you looked at the stoppage points in your file(s) with a hex
> > editor? Any non-printable non-ASCII characters other than newline
('\n')?
Your answer:
This box is fedora core 5 with sqlite3 3.3.3.
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
