A bit of background: I am working on a brewer's grain/malt specifications database app (and after that, similar for hops and yeast). After learning how to use Tcl to populate an SQLite3 database from ones I already had here (in a Tcl/Tk app), I am using an SQLite3 database in my apps.
I've seen a tutorial on SQLite3 for the Android that says (for read/write databases) to make a copy of the database into the Android's default location. Question: Given that the database is read-only, and the fact that, in order to copy it from one location to another, I already have to be able to read it, can I just leave it in the assets directory and read from it in that location instead of making a copy? It just seems that, if the database is already occupying space in RAM, and since I'm not actually changing it, why waste the time to copy it on the first run, and then verify it on every run after that? Comments? Thanks, --jim -- 73 DE N5IAL (/4) | "This 'telephone' has too many [email protected] | shortcomings to be seriously considered < Running FreeBSD 7.0 > | as a means of communication. The device ICBM / Hurricane: | is inherently of no value to us." 30.44406N 86.59909W | (Western Union internal memo, 1876) Point Lobos Photography Set 1 (Photo-posters): http://jdgapps.com -- 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
