Unless you plan on having different schemas for different situations (e.g., small screens vs. normal screens, English vs. Spanish), there is no particular gain from having them in string resources. And, resources are publicly visible to other applications.
This does not mean that string resources won't work, just that I'm not sure what you're gaining. On Sat, Mar 5, 2011 at 10:26 AM, Jay Bloodworth <[email protected]> wrote: > Where is the best place to store the "CREATE TABLE..." statement strings > for an app that uses a SQLite database? Most of the examples I have come > across include them directly in the source code. Is there a reason why > this is preferable to storing them as resources, say as a string array? -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android App Developer Books: http://commonsware.com/books -- 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
