04-13-2010 11:04 PM
why does RIM not recommend to use sqllite with eMMC with large databases?
is it because speed?
04-14-2010 08:07 AM
Where have you seen this recommendation?
What is eMMC?
04-14-2010 08:49 AM
If I recall correctly from the Super App webinar, Mike Kirkup specifically suggested SQL Lite as the preferred DataBase handler.
Also, is this what you meant?
http://www.micron.com/products/nand/managed-nand/i
The other pages that Google suggested for "eMMC" didn't seem to fit...
Anyway, hope that helps,
~Dom
04-14-2010 12:02 PM
straight from the SQLLITE DEMO app with JDE 5.0
* This sample application demonstrates the use of a SQLite database and the
* 'net.rim.device.api.database package'. A pre-configured database is included
* with the project and will be copied to the default root location (provided an
* SDCard is available) if a database does not already exist at that location.
* The default root for SQLite databases is 'file:///SDCard/databases/*project-name*'.
* Certain BlackBerry Smartphone devices are capable of creating databases in eMMC
* memory. However, using eMMC memory to store large databases is not recommended.
I assumed eMMC is multimedia card.
04-14-2010 01:40 PM
smiley wrote:I assumed eMMC is multimedia card
Safe assumption, since eMMC is a joint trademark of the MultiMediaCard Association and JEDEC. ![]()
04-14-2010 02:23 PM
I suspect that we are talking here about some devices (Bold 9000 for example) that have a system root in addition to the SDCard - and system points at internal memory rather than the SDCard. If so, I suspect the reason should not make these too big as it impinges on other internal uses for that space. But that is just a theory, I think we need some input from RIM here.
04-14-2010 11:28 PM
eMMC is referring to the extra internal memory that some of the newer devices have (Storm/Storm2,etc). I would assume that it says not to use this memory because it is the same memory used by the OS for processing, and Flash/NAND memory has a limited number of times that it can be written to before it starts to fail, which would proabaly brick the device (or at least faster). It probably has more to do with the random accessof the DB as well as read/erase/write cycle that is used to update data.
04-23-2010 11:29 AM
Here is the reasoning behind this recommendation:
I realize the requirements for an application may make these a moot point. For example an application that is targeted for a BlackBerry Bold 9000 and will have a 2 MB database would be best supported by storing its database on the eMMC.
We are going to modify this comment in the sample to clarify what we mean.