Cesar David Rodas Maldonado wrote:
please i need some help
Cesar,
I suspect that the tone of your messages and your insistence on getting
some sort of unspecified help has irked more than a few members of this
list.
I appreciate that English may not be your first language, but your
statement of the problem is not clear. And until there is a clearer
statement of the problem, I suspect you won't get any more help.
How are you accessing the database (i.e.are you using a wrapper)? Are
you using separate processes or threads to do the writes (i.e. inserts)
and reads (i.e. selects)? How often are you writing? How many records
are your writing at once (i.e. are your updates batched)? How often are
you reading? Which have higher priority, the reads or the writes?
As others have already tried to point out, SQLite does not allow another
process to read a database while one is writing it. It simply can't be
done. So one or the other will have to be delayed until the other is
completed (i.e. the accesses must be serialized). There are several ways
to do this depending upon on what, exactly, you are trying to do. You
can use an external mutual exclusion mechanism, you can use transactions
with retry loops, you can use a busy handler, etc.
SQLite can write data into a database and later read that data back out.
It can do it with lots of data, and it can do it quickly. But sometimes
there is more to it than just issuing insert and select statements.
Please lets us know more precisely what you are trying to do and what
isn't working. Then I'm sure someone will be able to help you. If you
won't invest some time to try to get the problem resolved, no one else
will either.
Dennis Cote
P.S. "couse" is not an English word. I think you should try "because"
instead.
