On 1 Dec 2012, at 3:22pm, dochsm wrote:
> My database is shared by many users on a network. As part of auto-updating my
> client applications via the web it might be necessary to alter some table
> structures / view sql or put extra data into tables inside the shared
> I have found that when using SQLite under Windows if you execute an update
> statement and then a select statement, the database is locked until the
> select statement is finished. How can I stop this from happening?
Note that you don't have to execute UPDATE before the SELECT to
reproduce
I have found that when using SQLite under Windows if you execute an
update statement and then a select statement, the database is locked
until the select statement is finished. How can I stop this from happening?
Here is a simple test program that simulates this situation. If you run
the
> -Original Message-
> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
> boun...@sqlite.org] On Behalf Of David de Regt
> Sent: vrijdag 30 november 2012 18:41
> To: General Discussion of SQLite Database
> Subject: [sqlite] Windows (slow) vs. iOS/OSX (fast) Performance
>
>
My database is shared by many users on a network. As part of auto-updating my
client applications via the web it might be necessary to alter some table
structures / view sql or put extra data into tables inside the shared sqlite
database. Problem is that the db might be in use at the time.
Qn1)
On Sat, Dec 01, 2012 at 06:00:59AM +0400, Уточкин Александр scratched on the
wall:
> Could you tell me please if it is normal that memory used by application
> goes like this:
>
> SQLite3_Prepare_v2 - Memory used changes slightly
> Binding values - Memory used changes slightly
> Loop with
Уточкин Александр wrote:
> Could you tell me please if it is normal that memory used by application
> goes like this:
>
> SQLite3_Prepare_v2 - Memory used changes slightly
>
> Binding values - Memory used changes slightly
>
> Loop with
Good day everybody!
Could you tell me please if it is normal that memory used by application
goes like this:
SQLite3_Prepare_v2 - Memory used changes slightly
Binding values - Memory used changes slightly
Loop with sq3lite_step - Memory used growths by 16Mb
sq3lite_finalize - Memory used
I have found a minor bug in the sqlite3 shell program. If you use .read to run
a
file with exactly two errors in it, it will exit from sqlite3 to the operating
system.
To demonstrate, I first create a file with two lines each of which causes an
(called e2.sql)
select nonexistentfunction();
You said that other people tested it, and verified it, so it's unlikely
that an Antivirus (or some other software - Inventory, or something
similar) might be problematic.
Another thing you can do is to fire up procmon (SysInternals) and watch
writes to your db. - they would happen from your
10 matches
Mail list logo