Dear Ross,
--------------------------------------------
From: Ross Altman <altman...@husky.neu.edu>
Sent: Tue, 14 Oct 2014 14:38:41 -0400
To: General Discussion of SQLite Database <sqlite-users@sqlite.org>
Subject: Re: [sqlite] Make a database read-only?
>
Thanks everyone for the helpful answers. Here's some context:
The database I have is for academic purposes. Research groups will need to
be able to download it in order to do large-scale scans using it as input,
so putting it in a wrapper (in PHP, say) isn't useful. But, I don't want
someone else to take it, add to it, and put it online somewhere else, so
that there are multiple versions floating around the web. I don't mind if
there are multiple COPIES, but I want to make sure that they're all the
same.
To a degree this sounds like the Streisand effect:
https://en.wikipedia.org/wiki/Streisand_effect
Pasting the sha256 is your best bet, but anyone who's going to verify the
sha256 can already dump the database as explained by Clemens Ladisch.
Thanks again,
Ross
--
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
