Roger, > Out of curiousity why do you want to know this? Note that even if a > database is opened at the SQLite level readonly it can still be written to > at the operating system level - an example would be recovering from the > journal.
I'm porting code from DBMS platforms that have grants and revokes. One of the functions gets a list of available tables and what SQL operations you can perform on them (select, insert, update, delete). A table in a database attached to read-only would have select privilges, but a table in a database attached read/write would have all four. > In terms of exporting information, I'd recommend making virtual tables > available rather than modifying existing pragmas. So, write a virtual table to that contains the information I've added to the pragma? That's possible, but I'd still have to go inside SQLite somehow to get the information in the first place. So, I'm not seeing a lot of advantage here. I have considered copying and renaming the pragmas to something like database_list2 and index_info2. Best, Peter _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
