When building a database query in the content provider SQLiteQueryBuilder.setProjectionMap(...) can be used to map the clients view of the content onto the actual database column names. This is nice as it lets the content provider expose its functionality without exposing the inner workings.
However in looking at the Notepad sample and online docs I see no mention of using the same technique when implementing update and delete. If the public view of the content provder needs to be remapped for queries then I feel that the same re-mapping should be done in update and delete. Am I missing something here? Do I have to parse the selection and selectionArgs parameters (of update and delete) and replace the logical names with the internal physical names? -- Richard -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
