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)); >> Filename, version, date and size put to another table with md5sum as a >> foreign key. Inspire with Git system or use it. > > I will have a look at Git. > Christoph If you planning version control system, you may select from completed systems, eg. Subversion, Git, Mercurial and Bazaar. -- Kit _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
