William,
This:
http://developer.android.com/reference/android/database/sqlite/SQLiteDatabase.html#setLockingEnabled(boolean)
suggests that thread-safe locking is enabled by default.
Are you turning it off somewhere, perhaps?
If not, I think you could try calling this method to explicitly enab
I have seen some other discussions on this issue for Sqlite and the
solution was to increase the busy timeout for the DB.
Anyone know how that is achieved on Android?
On Nov 2, 12:14 am, William Ferguson
wrote:
> I'm seeing the same thing.
>
> And to answer the questions:
> 1 - There is no other
I'm seeing the same thing.
And to answer the questions:
1 - There is no other app using my db, though it is accessed from both
my Activity and an IntentService within my app. Both of which needs
write access.
2 - I closed the cursor every time.
I cannot see any need for the entire DB to be locked
Hi gcstang,
Very basic but check the following:-
1- Is any other app using your DB?
2- Did you close the cursor every time when you opened it?
Thanks,
AJ
On Oct 25, 5:41 pm, gcstang wrote:
> ping, anyone that can answer this?
>
> On Oct 16, 10:58 am, gcstang wrote:
>
> > Here is the stack:
>
ping, anyone that can answer this?
On Oct 16, 10:58 am, gcstang wrote:
> Here is the stack:
>
> android.database.sqlite.SQLiteException:errorcode5:databaseislocked
> at
> android.database.sqlite.SQLiteStatement.native_execute(Native Method)
> at
> android.database.sqlite.SQLiteSta
Here is the stack:
android.database.sqlite.SQLiteException: error code 5: database is
locked
at
android.database.sqlite.SQLiteStatement.native_execute(Native Method)
at
android.database.sqlite.SQLiteStatement.execute(SQLiteStatement.java:
55)
at
android.database.sqlite.SQLi
Where is the error being thrown from? (You might include the
exception traceback.)
On Oct 15, 9:44 am, gcstang wrote:
> Has anyone encountered this and is there a solution to work around it?
>
> I'm creating a Thread and in that thread I open a database connection
> using the DBHelper, perform a
I use
synchronized(ExampleDbAdapter.class){mDb.insert/update/delete/query...} in
ExampleDbAdapter to avoid this. Let me know if there's a better way.
On Mon, Aug 24, 2009 at 10:58 AM, Armond Avanes wrote:
>
> So how can I create an in-memory database? I just took a quick look at the
> API and co
So how can I create an in-memory database? I just took a quick look at the
API and couldn't find any.
Cheersss,
Armond
> develop...@googlegroups.com] On Behalf Of Andrei
> Sent: Monday, August 24, 2009 7:35 AM
>
> If your write time take long i would try this
> I would create another in memory
If your write time take long i would try this
I would create another in memory database, attach it to yours.
In memory database table would have same schema.
You would write to in memory database and after done do insert into
db1.table as select * from db2.table
I did something similar but on desk
I forgot to mention that this exception happens (so far) from the service I
have for updating database (is executed every 24 hours).
Cheersss,
Armond
> Hi Guys,
>
> I have different background threads in my application, one doing
> periodical
> database updates, another responsible for doing lo
11 matches
Mail list logo
