Christopher Tate 61695ffcbc Make sure settings writes are permission checked correctly
The last bit of undoing the earlier tangle around query results having
observers under the calling user's identity.  We do *not* want to drop
calling identity in the call() processing; we want the table-based
permission checks at the point of the underlying db operations to be
performed against that identity.

Bug 7265610

Change-Id: Ie0c9331ebd0918262a0a32b5b03b876fc2a92ca3
2012-10-05 12:05:13 -07:00
2012-09-14 16:23:37 -07:00
2012-10-02 15:21:11 -07:00
2012-10-03 18:07:23 -07:00
2012-09-20 09:12:43 -07:00
2012-04-04 11:37:35 -07:00
Description
No description provided
21 GiB
Languages
Java 73.7%
Kotlin 14%
PowerBuilder 5.8%
C++ 5.2%
AIDL 1%