Re: [sqlite] Problem with SQLITE_BUSY

On 10/29/2013 10:32 PM, Normand Mongeau wrote: Hmm really? Odd thing is that although I do have a 10 second timeout as soon as C goes into a begin transaction A receives the SQLITE_BUSY error, in other words I don't see any 10 second delay. This, too, is consistent with my diagnosis. When

[sqlite] Performance measurement

Hi all, I would like to gain more knowledge on the performance measurments and (more specifically) their possible implications and maybe some Database theory to boot. The figures of interest are the statement quantitative values which return simple counters such as Table scans, Virtual

Re: [sqlite] Problem with SQLITE_BUSY

Hmm really? Odd thing is that although I do have a 10 second timeout as soon as C goes into a begin transaction A receives the SQLITE_BUSY error, in other words I don't see any 10 second delay. I'll try increasing the timeout. -Original Message- From: sqlite-users-boun...@sqlite.org

Re: [sqlite] Problem with SQLITE_BUSY

Actually I was mistaken (my apologies), A doesn't open a second connection, I thought it did but under this scenario it doesn't. So it simplifies my problem, yet I don't see what's wrong. Normand -Original Message- From: sqlite-users-boun...@sqlite.org

Re: [sqlite] Problem with SQLITE_BUSY

On 29 Oct 2013, at 10:26pm, Normand Mongeau wrote: > I have a situation where I always run into an SQLITE_BUSY error. Set your timeout to something very large (a million milliseconds ?) and see if the problem just turns into unexpected delays instead of errors. You

Re: [sqlite] Android - Occasional Error when closing a database

I insert the data using: SQLiteStatement myStatement = databaseWriter.compileStatement(statementString); myStatement.executeInsert(); After Richards reply I went back and enclosed all these in try finally blocks with myStatement.close(); now in the finally bracket. Guess I missed one

Re: [sqlite] Problem with SQLITE_BUSY

You haven't explained what the second connection in A is doing. My educated guess is, the two connections enter into a deadlock. This is possible when at least one connection starts as a reader and later attempts to write (the other could be a straight writer). The scenario goes like this: the

[sqlite] Problem with SQLITE_BUSY

Hi, I have a situation where I always run into an SQLITE_BUSY error. It's quite involved, here's the high picture: -3 processes (A, B and C) each have a connection to the same db. Everybody has a busy handler set for 5 seconds. -1 of these processes (A) opens more than one connection,

Re: [sqlite] Android - Occasional Error when closing a database

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/10/13 06:23, Matthew Dumbleton wrote: > I have noticed that occasionally, after the data is entered and the > transaction ended, the close method call produces an error 'unable to > close due to unfinalised statements' and logCat shows the

Re: [sqlite] System.Data.SQLite v1.0.89 Breaks My App(SQLite.interop.dll)

Denis Burke wrote: > > Apps works fine on 1.0.85, but with v1.0.89 I get the error noted at the > bottom. Switching back to 1.0.85 works fine again. Further investigation > finds that v1.0.85 does not have a separate SQLite.Interop.dll. These > functions were apparently separated from the main

[sqlite] System.Data.SQLite v1.0.89 Breaks My App (SQLite.interop.dll)

Apps works fine on 1.0.85, but with v1.0.89 I get the error noted at the bottom. Switching back to 1.0.85 works fine again. Further investigation finds that v1.0.85 does not have a separate SQLite.Interop.dll. These functions were apparently separated from the main DLL in a release after

Re: [sqlite] Database gets locked for other processes

"Martin Kropfinger" Am Tue, 29 Oct 2013 12:00:02 -0400 schrieb sqlite-users-requ...@sqlite.org: Date: Tue, 29 Oct 2013 14:51:08 +0100 From: Stephan Beal To: General Discussion of SQLite Database Subject: Re: [sqlite] Database gets locked for

Re: [sqlite] Database gets locked for other processes

Am Tue, 29 Oct 2013 12:00:02 -0400 schrieb sqlite-users-requ...@sqlite.org: > Date: Tue, 29 Oct 2013 14:51:08 +0100 > From: Stephan Beal > To: General Discussion of SQLite Database > Subject: Re: [sqlite] Database gets locked for other processes >

Re: [sqlite] Database gets locked for other processes

On Tue, Oct 29, 2013 at 1:52 PM, Martin wrote: > The program is running on Windows7. > ... The program runs parallel on multiple machines all sharing the same > SQLite-Database-file. Connecting multiple clients over a network share is a sure-fire way to corrupt your

Re: [sqlite] Android - Occasional Error when closing a database

On Tue, Oct 29, 2013 at 9:23 AM, Matthew Dumbleton wrote: > I have an android application using sqlite that starts with a database > being created and then filled with a lot of data. > I have noticed that occasionally, after the data is entered and the > transaction ended, the

[sqlite] Android - Occasional Error when closing a database

I have an android application using sqlite that starts with a database being created and then filled with a lot of data. I have noticed that occasionally, after the data is entered and the transaction ended, the close method call produces an error 'unable to close due to unfinalised statements'

Re: [sqlite] Database gets locked for other processes

Sounds like something changed in Qt 5.1.1 so that it is holding open a read transaction. The first process acquires the read transaction, which permits other processes to read but prevents anybody else from writing. I have no idea why Qt would do this, though. You can change to WAL mode, which

[sqlite] Database gets locked for other processes

Hi there! I have a program written in Qt and using the SQLite-drivers shipped with Qt. AFAIK those are the original SQLite-drivers. The program is running on Windows7. Originally the program was written using Qt4.8 (which came with SQLite 3.7.14.1). The program runs parallel on multiple machines

Re: [sqlite] Hex value with DEFAULT Constraint

Actually there are hex literals, but they are of type blob and don't convert to numeric. So if you were wishing for an equivalent to the C declaration "int c = 0xff;" you are out of luck. See requirement R-16625-30785-18660-34070-49109-22249-51329-26220 CREATE TABLE t1( t TEXT, -- text

Re: [sqlite] Feature Request: Binding Arrays

On Tue, Oct 29, 2013 at 2:06 AM, Olaf Schmidt wrote: > Am 16.10.2013 10:40, schrieb Dominique Devienne: > If I somehow missed a better work-around to this lack of array-binding, I'm > >> also interested of course, but obviously I'd prefer real array binding. >> > > Maybe

Re: [sqlite] Hex value with DEFAULT Constraint

On 10/29/2013 8:09 AM, techi eth wrote: Is it possible to attach hex value with DEFAULT constraint? There are no hex literals in SQLite, whether for use with DEFAULT constraint or otherwise. You will have to specify your numeric constants in decimal. -- Igor Tandetnik

[sqlite] Hex value with DEFAULT Constraint

Is it possible to attach hex value with DEFAULT constraint? I am getting return error code as SQLITE_ERROR & detail error message as "unrecognized token". ___ sqlite-users mailing list sqlite-users@sqlite.org

Re: [sqlite] vbscript and sqlltie

Am 27.10.2013 08:41, schrieb Joe Fuller: I’m trying t access sqllite database via vbscript. I don’t want to use odbc just ado.net. I'm pretty sure vbScript doesn't support .NET class-instancing directly, vbScript wants COM-(Dlls, to instantiate classes from). This is the sort of thing I’ve

Re: [sqlite] Feature Request: Binding Arrays

Am 16.10.2013 10:40, schrieb Dominique Devienne: If I somehow missed a better work-around to this lack of array-binding, I'm also interested of course, but obviously I'd prefer real array binding. Maybe I'm missing something - but if I'd have a lot of "InApp- MemAllocations" in the form of

Re: [sqlite] compiling the non-AMALGAMATION on visual studio

On Mon, Oct 28, 2013 at 10:38 PM, David Clark wrote: > I am trying to compile the source tree on visual studio with makefile.msc > and I get the following: > [...] > Why am I doing this: > I have a database lock error coming from a update query and I am not sure > why. So