I didn't, but I could have, by using authorizer function (relatively easy -- see sqlite3_set_authorizer), and setting it in the extension initialization function. Mind you, I generally feel if people are going to muck with the metadata, it's their own problem.
Peter ________________________________ From: Grace Simon Batumbya <grace.batum...@senecacollege.ca> To: General Discussion of SQLite Database <sqlite-users@sqlite.org> Cc: Peter Aronson <pbaron...@att.net> Sent: Tue, March 6, 2012 10:57:48 AM Subject: Re: [sqlite] Building an SQLite Extension: How to Persist Configurations/Variables for a database On 3/6/2012 12:04, Peter Aronson wrote: It's just basic SQLite reading and writing logic, like in here: http://www.sqlite.org/cintro.html > >Okay, I thought I needed to use some other functions since I was creating an >extension. Do you implement any logic prevent users from modifying the value in the table directly after it has been set? Grace Batumbya Research Assistant | Seneca CDOT Phone: 416-491-5050 x3548 cdot.senecac.on.ca _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
