Re: [sqlite] Stricter parsing rules

If it was called "PRAGMA strict_mode" or even "PRAGMA disable_dbl_quot_lit" you could reverse the check and then the default behavior would remain the same. --- On Fri, 11/16/12, NSRT Mail account. wrote: From: NSRT Mail account. Subject: Re:

Re: [sqlite] inserting record datinto mutliple tables with a composite primary key

This looks like a more or less complete solution for creating the tables and doing inserts. Primary table: CREATE TABLE Structure( 'id' INTEGER PRIMARY KEY, 'name' TEXT NOT NULL, 'filePath' TEXT NOT NULL, 'iH1' INTEGER NOT NULL, 'iH2' INTEGER NOT NULL, 'iH3' INTEGER NOT NULL,

Re: [sqlite] memory leak in transactions

rui wrote: > > I am seeing explosive memory growth when i am using transactions using > System.Data.SQLite. > The best way to address this issue is to utilize "using" blocks for any SQLiteCommand, SQLiteDataReader, and SQLiteTransaction objects used. That way, you won't have to wait until

Re: [sqlite] light weight write barriers

On 11/15/2012 11:06 AM, Ryan Johnson wrote: The easiest way to implement this fsync would involve three things: 1. Schedule writes for all dirty pages in the fs cache that belong to the affected file, wait for the device to report success, issue a cache flush to the device (or request ordering

Re: [sqlite] light weight write barriers

David Lang wrote: barriers keep getting mentioned because they are a easy concept to understand. "do this set of stuff before doing any of this other set of stuff, but I don't care when any of this gets done" and they fit well with the requirements of the users. Users readily accept that if the

Re: [sqlite] light weight write barriers

Ric Wheeler wrote: On 11/16/2012 10:06 AM, Howard Chu wrote: David Lang wrote: barriers keep getting mentioned because they are a easy concept to understand. "do this set of stuff before doing any of this other set of stuff, but I don't care when any of this gets done" and they fit well with

Re: [sqlite] memory leak in transactions

Thanks for your reply. I am using version 1.0.79.0 of System.Data.sqlite Here is how i am using it, i only use executescalar and executenonquery, let me know if you want to see how i pass the parameters etc. RunBigtransaction() { using (IDbTransaction tran =

Re: [sqlite] light weight write barriers

On Fri, 16 Nov 2012, Howard Chu wrote: David Lang wrote: barriers keep getting mentioned because they are a easy concept to understand. "do this set of stuff before doing any of this other set of stuff, but I don't care when any of this gets done" and they fit well with the requirements of