In my mainframe days, using IDMS/SQL, I limited user access to table data, down to the column level, based upon logged on userid. This was accomplished via database procedures. I'm new to SQLite, so don't know if it has any similar capabilities.
>________________________________ >From: Igor Tandetnik <itandet...@mvps.org> >To: sqlite-users@sqlite.org >Sent: Friday, July 15, 2011 9:24 PM >Subject: Re: [sqlite] Hidding records from the application > >On 7/15/2011 9:19 PM, san long wrote: >> Dear all, >> I have an idea related to the safety of the records in a table: if it is >> possible to hide some records in a table so the upper user application could >> not see them? >> For example: >> table food has content: >> 1, "food A" >> 2, "food B" >> I want to hide the record whose rowid is 2, so: >> sqlite> SELECT * from food; >> -------------------------------------------------- >> 1, "food A" >> --------------------------------------------------- > >How is SQLite supposed to know which application is allowed to see these >rows and which one isn't? Presumably, *someone* must be able to see >them, or else you can just delete them and be done with it. What exactly >makes an application "upper user application" (as opposed to "lower >system application", I guess)? >-- >Igor Tandetnik > >_______________________________________________ >sqlite-users mailing list >sqlite-users@sqlite.org >http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
