I could use some thoughts/suggestions on "what may be the best approach to handing multiple SQLite DBs for an Android app based upon a template DB?"
About the existing app - representing the issue of handling multiple DBs in Android:
As brief as possible, I have an existing Java-based Research DB app that allows a user to create a subject oriented database for research that requires the user to document a source for each note on a subject. A subject would be a single database. (blank.zip attached contains SQLite db examples)
So there is a blank template database (i.e. blank.db) that is copied and renamed to the subject the user chooses to research. The SQLite template database contains 11 tables, 10 relation-ally linked to a Notes table. The remaining 10 tables are Sources, Authors, Author_by_Source, Comments, Quotes, Terms, Topics, Files, File_by_Note, Questions. However, a user can delete, export, or import any database they wish except the blank.db and sample.db which come with the app.
What have I done:
I've have been reading and doing hands-on tutorials learning the Android C.R.U.D approach through the DatabaseHelper. I've also learned about the Asset folder and storing databases already created within a sub folder called databases. So this where I ask my question(s).
So the Discussion Questions:
What is the best way to handle creating new databases?
Can I manage everything through the Assets folder?
About the existing app - representing the issue of handling multiple DBs in Android:
As brief as possible, I have an existing Java-based Research DB app that allows a user to create a subject oriented database for research that requires the user to document a source for each note on a subject. A subject would be a single database. (blank.zip attached contains SQLite db examples)
So there is a blank template database (i.e. blank.db) that is copied and renamed to the subject the user chooses to research. The SQLite template database contains 11 tables, 10 relation-ally linked to a Notes table. The remaining 10 tables are Sources, Authors, Author_by_Source, Comments, Quotes, Terms, Topics, Files, File_by_Note, Questions. However, a user can delete, export, or import any database they wish except the blank.db and sample.db which come with the app.
What have I done:
I've have been reading and doing hands-on tutorials learning the Android C.R.U.D approach through the DatabaseHelper. I've also learned about the Asset folder and storing databases already created within a sub folder called databases. So this where I ask my question(s).
So the Discussion Questions:
What is the best way to handle creating new databases?
Can I manage everything through the Assets folder?