Hi Dave, Dave Dyer wrote:
I'm taking a test cut at converting a existing mysql database to sqlite. I dumped the mysql database, tweaked the prototype into slite format, and converted the escape characters in the data to standard sql format. Here's what happens when I attempt an import: sqlite> .read proto.txt sqlite> .read city-part.sql INSERT INTO city VALUES (112.0000,7617.0000,'Hartford',41.7640,-72.6860); SQL error: unable to open database file INSERT INTO city VALUES (52.0000,6583.0000,'Eindhoven',51.4500,5.4670); SQL error: unable to open database file INSERT INTO city VALUES (13.0000,5828.0000,'Bradford',50.5480,-4.6610); SQL error: unable to open database file ... These sql errors are random. Since there's no other activity affecting this database, I wouldn't expect any contention problem. Is there something I'm missing?
Without knowing the contents of proto.txt, I'd say you probably have defective RAM in your machine, or a defective harddrive. If your machine is a x86, you can Google memtest86 to get an excellent free tool for checking for RAM defects.
Oh yea, and this is EXTREMELY slow, presumably because I haven't wrapped the inserts in a transaction.
Very, very likely, that shuld be the cause of the slowness. Ulrik
