Hi Christian,
This is really interesting. What is the official definition of suspension?
On handheld devices, the device suspends itself every minute or so to save
battery life. All the user does is press the power button and the
application is back. Is that the level of suspension you are
Hi Dan,
Responses inline:
On 4/18/07, Dan Kennedy <[EMAIL PROTECTED]> wrote:
> At first I thought this had solved the problem, because all in house
testing
> runs beautifully. However, as soon as the device is sent to the field,
the
> error starts again. Unfortunately, it means that I have
> At first I thought this had solved the problem, because all in house testing
> runs beautifully. However, as soon as the device is sent to the field, the
> error starts again. Unfortunately, it means that I have never been able to
> catch this in debug. I did, however, change the error
; when you receive the first write error. This is (approximately) the
> > number
> > > of bytes
> > > the card can store (at that point in time) and falling.
> > >
> > > It seems some cards even return "read errors", when they hit a
> defect
gt; > upon read. Maybe the actual error code just gets lost/mangled on the
way
> > up
> > and the
> > actual error is just a simple read error ;) I've seen reports about
this
> > with some
> > digital cameras, which would not even let people view the pictures
taken
> a
gliche Nachricht-----
> Von: John Stanton [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 13. April 2007 23:44
> An: sqlite-users@sqlite.org
> Betreff: Re: [sqlite] Still getting "Insertion failed because database
is
> full." errors
>
> You might find some joy in the baby di
t-
Von: John Stanton [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 13. April 2007 23:44
An: sqlite-users@sqlite.org
Betreff: Re: [sqlite] Still getting "Insertion failed because database is
full." errors
You might find some joy in the baby disk drives such as installed in the
original ipod
You might find some joy in the baby disk drives such as installed in the
original ipods.
Can you substitute RAM with a battery backup if the memory card is
always in the device?
Joel Cochran wrote:
Thanks John and Dennis,
At least now I have something to look at. I will look into the CF
Thanks John and Dennis,
At least now I have something to look at. I will look into the CF problem
next.
The database itself gets generated on a PC and then transferred to the CF
Card. During testing and development, this could have been 20-30 times a
day, constantly erasing and recreating the
Flash memory is for read only access on a continuing basis but has a
certain number of write cycles to use for load it with data. For
example you might use it for backups or for loading and distributing
software or playing music but if you use it like a disk drive it will
hit its write limit
Joel Cochran wrote:
Or do you mean over the course of the lifetime of a CF card it can
only be
used so much? That might apply to this scenario, these cards have been
written over continuously for the last 6 months.
Joel,
Yes, that is exactly the problem. You should look at using a flash
Joel Cochran wrote:
John,
What do you mean by "general processing"? The database is on the CF card,
the application accesses the database. Other than what application
normally
do (select, update, insert, etc.), I'm not sure what else to tell you.
Or do you mean over the course of the
John,
What do you mean by "general processing"? The database is on the CF card,
the application accesses the database. Other than what application normally
do (select, update, insert, etc.), I'm not sure what else to tell you.
Or do you mean over the course of the lifetime of a CF card it can
That's what I was implying by my question.
-Ursprüngliche Nachricht-
Von: John Stanton [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 13. April 2007 20:56
An: [EMAIL PROTECTED]
Betreff: Re: [sqlite] Still getting "Insertion failed because database is
full." errors
Regular fl
Regular flash memory has a limited number of write cycles before it
fails. Are you hitting this problem by using it for general processing?
Joel Cochran wrote:
First, to answer John's question: the CF Card is a 1GB card, and the only
thing on the card is the SQLite Database (currently 509KB),
I would suggest including the SQL that was being processed, including all
parameters, in the error message. Even better would be to keep a log of all
SQL messages sent--perhaps keep the last X calls in memory and when an error
occurs log all of those calls and then the offending one.
log4net
First, to answer John's question: the CF Card is a 1GB card, and the only
thing on the card is the SQLite Database (currently 509KB), so I really
don't think it is a space problem. Unless you mean something else by Flash
memory?
Michael,
Yes, I am doing Selects, and using DataAdapters to fill
Are you sure that you are not exceeding the capacity of the flash memory
to handle writes?
Joel Cochran wrote:
Hi folks,
I had sent this message out a couple of weeks ago, and I am still searching
for a solution. I looked at the application design and made a modest
change: I now create a
18 matches
Mail list logo
