But be wary of the 1MB "gotcha" -- if the file is over 1MB you need to
name it ".jpg" or some such to prevent compression.
On Jan 2, 9:55 pm, Sarwar Erfan wrote:
> Put your pre-created and pre-populated database in assets. Then, copy to
> proper place in the first run (or when the db is not found
On Mon, Jan 3, 2011 at 1:50 PM, Pedro Duque wrote:
> I've read about prepopulting the database and looked good to me but I got
> worried about database upgrades...
>
No easy way to do upgrades. Check version on startup and download if
newer version is available is probably your best bet.
--
Yo
I've read about prepopulting the database and looked good to me but I got
worried about database upgrades...
On 3 de Jan de 2011, at 04:20, Zsolt Vasvari wrote:
> Creating 400 reconds should take no more than a few seconds if you
> bracket using transactions. It won't overload the system by an
Creating 400 reconds should take no more than a few seconds if you
bracket using transactions. It won't overload the system by any
stretch of the imagination.
Whether to go with the asset or create the database "on-the-fly"
should depend on your app, but either way is fine.
On Jan 3, 11:49 am,
Put your pre-created and pre-populated database in assets. Then, copy to
proper place in the first run (or when the db is not found where it
was supposed to be copied.
This link helped me:
http://www.reigndesign.com/blog/using-your-own-sqlite-database-in-android-applications/
There are other exa
5 matches
Mail list logo
