I noticed the same thing as Luiz. If I am not currently editing the database through the IDE, it should not be keeping a lock on the DB (which is why I wanted to submit a bug report). It's perfectly fine for it to keep it open for reading 24/7, though.
On Fri, Jan 8, 2010 at 5:24 AM, Luiz Americo Pereira Camara < luiz...@oi.com.br> wrote: > Luca Olivetti escreveu: > > En/na Michael Van Canneyt ha escrit: >> >>> >>> >>> On Tue, 5 Jan 2010, Matt Shaffer wrote: >>> >>> I thought I would just do a little update. I've been successfully able >>>> to write now, BUT, I don't believe the SQLdb components were really keeping >>>> SQLite in mind (the >>>> db I'm using). You see, Lazarus opens a connection to the SQLite >>>> database, preventing my app that's running (for debugging purposes) from >>>> writing. So I have to build >>>> the app, close Lazarus, then run my app... Should I file a bug report >>>> for this? >>>> >>> >>> No. >>> >>> It is a limitation of sqlite. >>> >> >> Then why zeosdbo has no such issue? >> > > It seems that Sqldb is keeping an transaction open even for reading > (Select) the data. I don't know in other DB, but in sqlite is not necessary > the transaction to read data. > > It's possible to have multiple connections reading the data at the same > time. Write blocks other connections from accessing the db. > > Luiz > > > -- > _______________________________________________ > Lazarus mailing list > Lazarus@lists.lazarus.freepascal.org > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus >
-- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
