On Tue, 13 May 2014 13:43:09 +0200 Ralf <[email protected]> wrote:
> A "File" splits its content into several fixed-sized encrypted blocks > and stores those blocks on some kind of storage. > At any point in time, it is guaranteed, that no other process will > interfere and use those blocks, so we don't need any locking > mechanisms. Why involve SQLite, exactly? You already have an object that can write to a file, no need for transactions, and no desire to decompose that object into columns and rows to share with other processes/users. You seem to think each such object is not just a row in a table, but an entire database. > I would like to avoid using temporary files. doesn't leap out as a case for SQLite. Whatever complexity you avoid with temporary files will surely be met tenfold for VFS support. --jkl _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
