Damien, At 09:18 08/10/2016, you wrote:
Password protecting it is also good on many levels - if the database is to be used online then it is needless to say that authentication would be required for various people to view it.
SQLite can't be put "online" per se. It will then be the duty of the host software layer (website software or equivalent using some other protocol) to accept only users having been granted access.
Even if I decide to make it local only, there is the possibility that anyone sharing the computer or network may peruse the database when you don't want them to.
That's the reason why OSes provide user login and file access rights. Again this is external to SQLite and its DB file(s). Also please note that SQLite is not a client-server engine, so access thru a LAN is prone to fail due to network file locking being poorly implemented.
Alternatively you can also use strong DB encryption with or without adding the authentication function. Google SQLite encryption and you'll find a number of answers, some of them correct.
JcD _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
