Re: [sqlite] Disk I/O utilization

2016-12-12 Thread Keith Medcalf
On Monday, 12 December, 2016 18:24, Vince Scafaria wrote: > Our application does a lot of SQLite read/write in a background process. > On some environments this hammers the disk I/O (e.g. Task Manager -> > Disk). Do you have suggestions on how we might minimize this? >

[sqlite] Disk I/O utilization

2016-12-12 Thread Vince Scafaria
Our application does a lot of SQLite read/write in a background process. On some environments this hammers the disk I/O (e.g. Task Manager -> Disk). Do you have suggestions on how we might minimize this? Perhaps related, one operation that seems to use a lot of the Disk I/O is when we use

Re: [sqlite] Disk I/O utilization

2016-12-12 Thread Simon Slavin
On 13 Dec 2016, at 1:23am, Vince Scafaria wrote: > Our application does a lot of SQLite read/write in a background process. On > some environments this hammers the disk I/O (e.g. Task Manager -> Disk). Do > you have suggestions on how we might minimize this? Batch them

Re: [sqlite] Bug report + fix: SQLite 3.11+ broken on EBCDIC systems

2016-12-12 Thread Bradford Larsen
> > On Sun, Dec 11, 2016 at 20:42 Richard Hipp wrote: > > SQLite only uses the "[" character as a compatibility quoting > > mechanism for SQL Server. Maybe the solution is for [...] quoting to > > simply not work on EBCDIC systems? > > > > -- > > D. Richard Hipp > >

Re: [sqlite] Disk I/O utilization

2016-12-12 Thread Quan Yong Zhai
1. The latest SQLite improved REPLACE operation, It's alot faster now. 2.use SAVEPOINT to batch transactions. They'll save many IO. 发自我的 Mobile Phone 发件人: Vince Scafaria 发送时间: ‎2016/‎12/‎13 9:24 收件人:

Re: [sqlite] Bug report + fix: SQLite 3.11+ broken on EBCDIC systems

2016-12-12 Thread Scott Hess
On Mon, Dec 12, 2016 at 9:30 PM, Bradford Larsen wrote: > An alternative possibility would be to revert to the pre-3.11 tokenizer on > EBCDIC systems. If I recall, the old tokenizer used a big switch statement > with character literals instead of the 'aiClass' table. I

[sqlite] System.Data.SQLite -> ChangePassword 2nd time has opposite behavior

2016-12-12 Thread Baugher, Melody
My SQLite databases are encrypted at build time. Small tools were developed to remove or apply the password to all 9 databases after build to facilitate the work of the database developers. The tools run the following bit of code against each database: string activatePragma = "PRAGMA

Re: [sqlite] System.Data.SQLite -> ChangePassword 2nd time has opposite behavior

2016-12-12 Thread Simon Slavin
On 12 Dec 2016, at 1:00pm, Baugher, Melody wrote: > Starting with an encrypted database, if I run this code twice in a row with > applyPassword=false, the password is removed the first time but then applied > the second time. Your program is weird and buggy. There is

Re: [sqlite] Run non-data producing statement just once to test UDF

2016-12-12 Thread Hick Gunter
Select AddOne( ); -Ursprüngliche Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Bart Smissaert Gesendet: Sonntag, 11. Dezember 2016 22:39 An: General Discussion of SQLite Database Betreff: [sqlite]

Re: [sqlite] System.Data.SQLite -> ChangePassword 2nd time has opposite behavior

2016-12-12 Thread Jens Alfke
> On Dec 12, 2016, at 5:00 AM, Baugher, Melody wrote: > > string passwordPragma = "PRAGMA key='" + password + "';"; Not quoting the password string leaves you open to SQL injection attack. This probably isn’t an issue in an internal development tool, but if there’s

Re: [sqlite] Run non-data producing statement just once to test UDF

2016-12-12 Thread Bart Smissaert
> Select AddOne( ); Yes, that might be the best option indeed. Still though it needs then to detect what the function does to supply the right arguments and to construct the right statement in code. I solved my problem in a different way. RBS On Mon, Dec 12, 2016 at 12:12 PM, Hick Gunter

Re: [sqlite] Error code for VT xColumn()/xRowid() if row does not exist?

2016-12-12 Thread Dan Kennedy
On 12/13/2016 01:47 AM, Bob Friesenhahn wrote: I am reworking code for a virtual table module and need to provide proper error codes from the xColumn() and xRowid() callbacks for the case where the row id does not exist, or the current row goes away. This problem occurs because the current

[sqlite] Error code for VT xColumn()/xRowid() if row does not exist?

2016-12-12 Thread Bob Friesenhahn
I am reworking code for a virtual table module and need to provide proper error codes from the xColumn() and xRowid() callbacks for the case where the row id does not exist, or the current row goes away. This problem occurs because the current virtual table module implementation does not lock

Re: [sqlite] Error code for VT xColumn()/xRowid() if row does not exist?

2016-12-12 Thread Bob Friesenhahn
On Tue, 13 Dec 2016, Dan Kennedy wrote: Perhaps SQLITE_NOTFOUND is a correct return code, but the documentation does not address return codes from virtual table modules. What is the correct code to return? If a cursor is being navigated, then I would prefer that the cursor continue to the