Re: [sqlite] System.Data>SQLite locking problem

I can confirm that the problem only exist when the database is encrypted. On Sat, Sep 15, 2012 at 11:00 AM, Serge Fournier wrote: > I work with an encrypted database and it look like it could be part of the > problem. > > > On Wed, Sep 12, 2012 at 3:05 PM, Serge Fournier

Re: [sqlite] System.Data>SQLite locking problem

Doing more testing on this I can say that I have the same problems with Windows 7. On Wed, Sep 12, 2012 at 8:08 AM, Serge Fournier wrote: > The thing here is that my code was working perfectly with the prior > version of the library and Windows 7. > The same code with 1.0.82

Re: [sqlite] System.Data>SQLite locking problem

The thing here is that my code was working perfectly with the prior version of the library and Windows 7. The same code with 1.0.82 and Windows 8 doesn't work anymore. I cannot use your solution, because the way my appliation works; it creates the database at first run and miust be able to run on

Re: [sqlite] System.Data>SQLite locking problem

Did you try it with a Windows 8? I have a feeling that the problem is more with this OS then the library. Here's something simple that doesn't work: SQLconnect.ConnectionString = "Data Source=" & Application.StartupPath & "\data.db;" SQLconnect.SetPassword(infoConnection) SQLconnect.Open()

Re: [sqlite] System.Data>SQLite locking problem

I've experienced this problem in the past. According to here, I found a solution. *Brandon's Tips on How to Unlock SQLite Databases* 1. Open a command line prompt window. 2. Type *sqlite* *dbname*.sqlite in the command line prompt, replacing "dbname"

Re: [sqlite] System.Data>SQLite locking problem

Serge Fournier wrote: > > Simply put, it's only possible to open a database once in the application > for writing; it's like the lock > doesn't get released until the application is closed. > I'm unable to reproduce the issue you describe here. Could you show us some sample code that

Re: [sqlite] System.Data>SQLite locking problem

Yes, all command have been disposed; everything works until I close the connection. Then when I open it again it the same application; either I get a "database is locked" when trying to write to it or I get "SQL queries are still processing" when I just opened it and send a VACUUM pragma to it.

Re: [sqlite] System.Data>SQLite locking problem

Serge Fournier wrote: > > Simply put, I open a database and then close it in an application then I > reopen it again, > I cannot write to it anymore; it is always locked. I tried doing a close, > dispose and shutdown > to my connection and then reopning it and do a simple vaccum; it tell me >

[sqlite] System.Data>SQLite locking problem

Hi, I'm not sure if it's Windows 8 or the latest version of the library (1.0.82) but I have a new problem with the same code that was working before. Simply put, i I open a database and then close it in an application then I reopen it again, I cannot write to it anymore; it is always locked. I

Re: [sqlite] SQLite locking problem with mozStorage

On 16 Aug 2009, at 11:55am, Sebastian Arcus wrote: > Just to thank you both for your suggestions and to let you know the > problem is solved. I'm glad you solved it, and thanks for your thanks. In a week like this one it's nice to know I'm doing someone some good somewhere. > I've tried

Re: [sqlite] SQLite locking problem with mozStorage

Hi Simon and Roger, Simon Slavin wrote: > On 15 Aug 2009, at 9:58am, Sebastian Arcus wrote: > > >> I've just noticed another interesting thing. A read operation after a >> write on same table (like a SELECT statement after an INSERT) works >> perfectly fine - instantly. Which is bizarre, as I

Re: [sqlite] SQLite locking problem with mozStorage

On 15 Aug 2009, at 9:58am, Sebastian Arcus wrote: > I've just noticed another interesting thing. A read operation after a > write on same table (like a SELECT statement after an INSERT) works > perfectly fine - instantly. Which is bizarre, as I would have > expected a > write to keep a much

Re: [sqlite] SQLite locking problem with mozStorage

Roger Binns wrote: > > Sebastian Arcus wrote: > >> Hi and thanks for the suggestion. I did as you advised and ran 'vmstat >> 1' in a terminal. Very little activity - maybe 20-40kb every 6-7 seconds >> on the bo - pretty much nothing on bi. Also, zeros all around on so/si. >> > > That

Re: [sqlite] SQLite locking problem with mozStorage

Roger Binns wrote: > > Sebastian Arcus wrote: > >> Hi and thanks for the suggestion. I did as you advised and ran 'vmstat >> 1' in a terminal. Very little activity - maybe 20-40kb every 6-7 seconds >> on the bo - pretty much nothing on bi. Also, zeros all around on so/si. >> > > That

Re: [sqlite] SQLite locking problem with mozStorage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sebastian Arcus wrote: > Hi and thanks for the suggestion. I did as you advised and ran 'vmstat > 1' in a terminal. Very little activity - maybe 20-40kb every 6-7 seconds > on the bo - pretty much nothing on bi. Also, zeros all around on so/si.

Re: [sqlite] SQLite locking problem with mozStorage

Roger Binns wrote: > Sebastian Arcus wrote: > >> The SQLite documentation talks about entire database locks by operations >> of the order of milliseconds - 10 seconds seems a long way off. >> > > There is a possible but unlikely cause for what you are seeing. In order to > ensure the

Re: [sqlite] SQLite locking problem with mozStorage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sebastian Arcus wrote: > The SQLite documentation talks about entire database locks by operations > of the order of milliseconds - 10 seconds seems a long way off. There is a possible but unlikely cause for what you are seeing. In order to ensure

[sqlite] SQLite locking problem with mozStorage

Hi all, I'm using the mozStorage implementation from Mozilla foundation, with Javascript and XUL (for the UI) to build a business-type app. I'm having this problem where I seem to get a lock of about 10 seconds after a read operation on a table, before I can perform a write operation on the

Re: [sqlite] locking problem

Do you have posix-locks enabled with your glusterfs? If you have use regular Sqlite locking logic and hope that the locks work properly. Lanyi Zoltan wrote: > Hello! > > I have shared disc system with glusterfs. > When i read or write on this disc system then i get error: database is locked >

[sqlite] locking problem

Hello! I have shared disc system with glusterfs. When i read or write on this disc system then i get error: database is locked But i not get error if i'd like read or write another program. (php write to text file, etc.) I have sqlite3. Somebody help me? Thanks, Zoltan A szexjátékoktól a

Re: [sqlite] locking problem under windows

On 12/11/06, "LEGRAND, Véronique" <[EMAIL PROTECTED]> wrote: I found in the sqlite3 documentation that there were locking problems when several processes running on different machines where trying to access an sqlite3 database located on an NFS filesystem and that this problem could be solved

[sqlite] locking problem under windows

I found in the sqlite3 documentation that there were locking problems when several processes running on different machines where trying to access an sqlite3 database located on an NFS filesystem and that this problem could be solved by running the "nfslockd" daemon. As I encounter the same

Re: [sqlite] locking problem (on insert inside callback)

Nah, ignore that, I was talking garbage... Using the view is a neater way of doing that select statement, but you still need to create the temp table to avoid the locking issues... Rachel On 03/12/05, Rachel Willmer <[EMAIL PROTECTED]> wrote: > (Replying to my own email so I can find this

Re: [sqlite] locking problem (on insert inside callback)

(Replying to my own email so I can find this answer again via google in the future...) I have an even better solution... CREATE VIEW NewView AS SELECT * FROM table1 LEFT JOIN table2 on table1.field=table2.field WHERE table2.field is NULL; Works just fine... Cheers Rachel Back In Oct, I asked:

Re: [sqlite] locking problem (on insert inside callback)

> Solution 1 is to use a TEMP table: > > CREATE TEMP TABLE diffs AS > SELECT * FROM table1 LEFT JOIN table2 ; > SELECT * FROM diffs; -- Insert into table1 in the callback; > DROP TABLE diffs; that sounds like the answer for me thanks Rachel

Re: [sqlite] locking problem (on insert inside callback)

> I'm not sure I understand your logic. Your left join > indicates that there are records missing from table2, > so I would expect that you want to insert the missing > records into table2. Assuming that's what you meant, > > insert into table2 > select * from table1 > where table1.field not

Re: [sqlite] locking problem (on insert inside callback)

> SELECT * FROM table1 LEFT JOIN table2 on table1.field=table2.field > WHERE table2.field is NULL > > So far, so good, I get the records I want. Then in the callback, I try > > INSERT INTO table1 etc... I'm not sure I understand your logic. Your left join indicates that there are records missing

Re: [sqlite] locking problem (on insert inside callback)

Why do it in the call back? Why not just do it in sql: CREATE TEMP TABLE diffs AS SELECT * FROM table1 LEFT JOIN table2 ; insert into table1 SELECT * FROM diffs; -- Insert into table1 DROP TABLE diffs; On 10/14/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Rachel Willmer <[EMAIL

Re: [sqlite] locking problem (on insert inside callback)

Rachel Willmer <[EMAIL PROTECTED]> wrote: > Hi, apologies if this is a trivial question, but I'm a newbie to > sqlite3. (very impressed so far) > > I want to search two tables which should contain the same records and > add any that are missing from the second into the first. > > So I do > >

[sqlite] locking problem (on insert inside callback)

Hi, apologies if this is a trivial question, but I'm a newbie to sqlite3. (very impressed so far) I want to search two tables which should contain the same records and add any that are missing from the second into the first. So I do SELECT * FROM table1 LEFT JOIN table2 on