Hello Joel,
You got me right. Going to suspend either happens when the user presses
the power key or the device automatically powers down after the
specified idle timeout has been reached.
The way to handle those events is quite tricky and device dependent.
Normally, the device manufacturer provi
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 tal
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 n
Hello Joel!
We were faced with similar problems in the field, too. Those were more
general ones with PCMCIA/CF/SD cards.
The reason was that the mobile devices (different device types with
Windows CE 4.1 and 5.0) doesn't handle the access to removable media
gracefully when the device is going to
> 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 reporti
: [sqlite] Still getting "Insertion failed because database is
full." errors
I've had him sit beside my in my office and attempt to recreate it, both
using his device and mine, but it never happens. Actually, I did get it to
happen once on his machine, but I was not connected to my PC,
tors with spares. Finally you determine the file
size
> of
> > > the
> > > card,
> > > 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.
&g
gt; It seems some cards even return "read errors", when they hit a
defective
> > sector
> > 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
bytes
> > the card can store (at that point in time) and falling.
> >
> > It seems some cards even return "read errors", when they hit a
defective
> > sector
> > upon read. Maybe the actual error code just gets lost/mangled on the
way
> > up
> > and the
&
not even let people view the pictures taken
a
> minute
> ago.
>
> Mike
>
> -Ursprüngliche Nachricht-
> Von: John Stanton [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 13. April 2007 23:44
> An: sqlite-users@sqlite.org
> Betreff: Re: [sqlite] Still getting "Inse
t even let people view the pictures taken a
minute
ago.
Mike
-Ursprüngliche 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." erro
w the pictures taken a
minute
ago.
Mike
-Ursprüngliche Nachricht-
Von: John Stanton [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 13. April 2007 23:44
An: [EMAIL PROTECTED]
Betreff: Re: [sqlite] Still getting "Insertion failed because database is
full." errors
You might find some jo
I program embedded systems using microcontrollers on occasions. The
method there is to store programs and tables in flash and dynamic data
in RAM. Perhaps you can partition your application that way. With
Sqlite you could have two databases, one with static tables in flash and
the other in R
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 pro
Well then I am certainly using it for general processing. Perhaps I should
explore the possibility of using the machine memory, although especially
once we get in to image processing I'm not sure that will be sufficient.
Thanks,
Joel
On 4/13/07, John Stanton <[EMAIL PROTECTED]> wrote:
Flash
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 e
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 a
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 fi
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 lifeti
I think it is also the case that flash cards write pretty slowly,
and there is a finite buffer of pending writes. Your unexpected
write failure may be because you're writing too fast. Depending
on the driver and access mode, the writes might throw this
error rather than block your process.
You
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
Regul
e the file system is
hitting a bad sector.
Is this running in a transaction?
Mike
-Ursprüngliche Nachricht-
Von: Joel Cochran [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 13. April 2007 17:46
An: [EMAIL PROTECTED]
Betreff: [sqlite] Still getting "Insertion failed because database is
6
An: [EMAIL PROTECTED]
Betreff: [sqlite] Still getting "Insertion failed because database is full."
errors
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
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 h
Freitag, 13. April 2007 17:46
An: [EMAIL PROTECTED]
Betreff: [sqlite] Still getting "Insertion failed because database is
full."
errors
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 mod
Mike
-Ursprüngliche Nachricht-
Von: Joel Cochran [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 13. April 2007 17:46
An: [EMAIL PROTECTED]
Betreff: [sqlite] Still getting "Insertion failed because database is full."
errors
Hi folks,
I had sent this message out a couple of weeks ago,
qlite] Still getting "Insertion failed because database is
full." errors
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 f
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 sing
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 single SQLiteConnection and use it from start to
finish of the application. Previously I was creating multiple connec
30 matches
Mail list logo
