Am 04.03.2012 10:31, schrieb Kit:
2012/3/4 Christoph P.U. Kukulies<k...@kukulies.org>:
Thanks for the ideas. The problem is with md5sum clashes: all files with 0
bytes have the same md5sum.
Also files with same contents have the same md5sum but may have a different
name.
That's no problem. if you put names to another table, you may share one content.
Normalize. One cell, one atomic information. You may use md5sum as
"text primary key" or you may define PRIMARY
KEY(filename,md5sum,size).
Interesting. How would that work syntaxwise? I mean, at table creation time?
CREATE TABLE dir(filename text, md5sum text, size int, content blob,
PRIMARY KEY(filename,md5sum,size));
Coming back to your suggestion using PRIMARY KEY(filename,md5sum,size),
how would I
address this PRIMARY KEY, example:
I'm building a table
CREATE TABLE candidate (?,client TEXT, md5sum TEXT, basename TEXT, size
INT, ...some other stuff )
The ? should stand for the - is that FOREIGN KEY? - key in the dir-TABLE
which is formed of filename,md5sum,size.
--
Christoph
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
