>I want to make things clear. there are some rules in my system, such >as : process whose name is proc_host can see all the records, and >process whose name is proc_client1 can see all the records except >rowid 1.
First, keep away of relying on rowid values since they may change if you don't create an INTEGER primary key yourself. That said, I have a feeling you don't expose all your requirements. Now from what you've told, what I would do is encode the sensitive columns of your "protected" row(s) with any proven standard of your choice. Share the key with all privileged processes and leave the other processes in the bush. Eventually, have a boolean column called "secret_row" to sort that out and you're home. Whatever OS you use, you can probably have access to an easy-to-use system call to perform on the fly encryption. Alternatively you can also code a simple known one yourself (relying on a proven algorithm) in your application. -- <mailto:j...@q-e-d.org>j...@antichoc.net _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
