I have a large (1.46 GB!) SQLite database (v2) with two tables:

CREATE TABLE TB_FileRecords (pszFilename TEXT PRIMARY KEY, nFileSize
INTEGER, nFileSignature TEXT);

CREATE TABLE TB_SignatureRecords (nFileSignature TEXT PRIMARY KEY, nFileDate
INTEGER ); 

1. I dumped the database into a text file, Data_full.sql= 949 MB 
2. I also deleted the first table and dumped the data into another text file
(Data_TB_SR.sql) which is only 532 MB.

I have another small database (new.db3; v3; 4 KB) with 1 table:
CREATE TABLE TB_Signature (Filename TEXT, FileSignature TEXT, FileSize
INTEGER, FileDate INTEGER, PRIMARY KEY (FileSignature,FileSize)); 

The goal is to read the dumped data (e.g. Data_TB_SR.sql) into new.db3;
sqlite3 new.db3
.read data_tb_sr.sql

==> After several hours of reading the data I start getting error messages:
SQL error: column nFileSignature is not unique

I tried to import data_tb_sr.sql in "SQLite Database Browser.exe" to
visualize the data, but got an error at line 66404453 and then the program
crashed. 

I tried to look at the data using a text editor (Professional Notepad),
and the data looked ok, nothing different at line 66404453 (data appears
unique).
Total number of lines in data_tb_sr.sql is 6641026 (including the last
"Commit;")

Maybe there is nothing wrong with the database, but I am running into a
limit of SQLite? Maybe the number of lines in a table is limited to
6640453??

Any suggestions of how to fix this so that I can read in the data in new.db3
w/o errors?

Also, how can I check if the data in the updated new.db3 is OK even though I
got errors?
I opened the updated new.db3 with "SQLite Database Browser.exe", but had
problems when trying to view the large table TB_SignatureRecords as the
program crashes..
-- 
View this message in context: 
http://www.nabble.com/MAX-SQLite-Size---Corrupt-Database-tf2579250.html#a7190256
Sent from the SQLite mailing list archive at Nabble.com.


-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to