Timeline for Android SQLiteOpenHelper time-consuming onCreate, need progress bar on first run
Current License: CC BY-SA 3.0
Post Revisions
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 23, 2016 at 9:09 | history | edited | Willi Mentzel | CC BY-SA 3.0 |
deleted 15 characters in body
|
| Aug 20, 2014 at 6:44 | comment | added | CL. | Copying a single block of data is likely to be faster (and simpler) than creating the database structure on the fly. | |
| Aug 20, 2014 at 5:48 | vote | accept | Philippe Le Point | ||
| Aug 19, 2014 at 23:39 | answer | added | MarkJ | timeline score: 4 | |
| Aug 19, 2014 at 19:27 | answer | added | Simas | timeline score: 2 | |
| Aug 19, 2014 at 19:11 | comment | added | Philippe Le Point | @CL - that's not possible. The only way to do this is to ship said .db file, and literally open it and copy it byte by byte (buffered blah blah) on onCreate, you gain nothing or very little compared to the SQL loading approach. | |
| Aug 19, 2014 at 19:09 | comment | added | Indra Kumar S | @CL is that possible ? Can you recommend any tutorials or blogs.... Im hearing for the first time | |
| Aug 19, 2014 at 19:07 | comment | added | CL. | Why don't you ship the app with a precreated database file? | |
| Aug 19, 2014 at 19:06 | history | asked | Philippe Le Point | CC BY-SA 3.0 |