On Tue, Dec 21, 2010 at 2:46 PM, Tobiah <[email protected]> wrote: > Oh I see, so that would eliminate any worries of say, sql injection > attack right off?
I doubt it defends against "little Bobby Tables" scenarios, though I have not tried it. http://xkcd.com/327/ That being said, SQL injection would seem unlikely to be a problem in a mobile app, simply because the data they would attack would be their own. > Is there any other reason that one would go > through this? Any performance gain, etc? Convenience. Beats doing the string concatenation and apostrophe-escaping yourself. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 1.9 Available! -- 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
