Re: [sqlite] Corrupting pointers to the lookaside smallacator

On 11/26/2014 06:47 AM, Ward Willats wrote: We are compiling the 3.8.7.1 using clang arm64 for iOS. Following set: #define SQLITE_ENABLE_COLUMN_METADATA 1 #define HAVE_INTTYPES_H 1 #define HAVE_STDINT_H 1 #define HAVE_USLEEP 1 #define SQLITE_DEBUG 1 #define SQLITE_MEMDEBUG 1 WAL mode. In

[sqlite] Corrupting pointers to the lookaside smallacator

We are compiling the 3.8.7.1 using clang arm64 for iOS. Following set: #define SQLITE_ENABLE_COLUMN_METADATA 1 #define HAVE_INTTYPES_H 1 #define HAVE_STDINT_H 1 #define HAVE_USLEEP 1 #define SQLITE_DEBUG 1 #define SQLITE_MEMDEBUG 1 WAL mode. In MallowRaw(), very rarely, seeing the lookaside

Re: [sqlite] Testing the 'I' in ACID

On 11/25/2014 5:41 PM, Simon Slavin wrote: Fair point. I should have written 'writing concurrency'. I would be interested in anything you have to say about the article I referred to. I don't see much in the way of reasoning in that article, and I'm too lazy to look at the code. Insofar as

Re: [sqlite] Testing the 'I' in ACID

On 25 Nov 2014, at 10:39pm, Igor Tandetnik wrote: > On 11/25/2014 5:32 PM, Simon Slavin wrote: >> SQLite doesn't support massive concurrency because it locks the entire >> database during changes. > > Not entirely true. WAL mode allows one writer working concurrently with

Re: [sqlite] Testing the 'I' in ACID

On 11/25/2014 5:32 PM, Simon Slavin wrote: SQLite doesn't support massive concurrency because it locks the entire database during changes. Not entirely true. WAL mode allows one writer working concurrently with multiple readers. -- Igor Tandetnik

[sqlite] Testing the 'I' in ACID

The 'I' in ACID stands for 'isolation'. In SQLite terms it means that a change made in one transaction doesn't affect another until the transaction is committed, at which point it does affect the database and transactions made afterwards. SQLite doesn't support massive concurrency because it

Re: [sqlite] Using Sqlite3 as a Change Time Recording Data Store in Glusterfs

On Sun, 23 Nov 2014 14:34:23 -0500 (EST) Joseph Fernandes wrote: > Ok I get it now. Yes we are using a single db connection object, But > few questions, > 1) how would making sqlite3 single thread that improve the > performance? Is there a special advantage in this mode

Re: [sqlite] Infinite loop in sqlite3VdbeSorterWrite when sorting big data

On 11/26/2014 12:41 AM, Marcin Sobieszczanski wrote: Do you have a large cache-size configured? Yes: PRAGMA cache_size = 10 PRAGMA page_size = 16384 Thanks for reporting this. I think it should be fixed here: http://www.sqlite.org/src/info/623827192532f08b Dan.

Re: [sqlite] System.Data.SQLite (v1.0.94.0) - Which encryptionalgorithm is used?

Krenn Christoph wrote: > > However I would like to know which encryption algorithm is used by > System.Data.SQLite, v1.0.94.0? > The legacy encryption support in System.Data.SQLite uses the CryptoAPI with the constants PROV_RSA_FULL and MS_ENHANCED_PROV, as described here:

[sqlite] System.Data.SQLite (v1.0.94.0) - Which encryption algorithm is used?

Hi, We're using an SQLite database together with System.Data.SQLite in a .NET solution. The database should be encrypted. This can be easily achieved using the SetPassword / ChangePassword methods in the System.Data.SQLite.SQLiteConnection class. However I would like to know which encryption

Re: [sqlite] Infinite loop in sqlite3VdbeSorterWrite when sorting big data

> Do you have a large cache-size configured? Yes: PRAGMA cache_size = 10 PRAGMA page_size = 16384 ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Infinite loop in sqlite3VdbeSorterWrite when sorting big data

On 11/25/2014 02:53 AM, Marcin Sobieszczanski wrote: Hi I work with sqlite files that have a few gigabytes of simple data. Almost all of the data sits in one table that has 9 non-null integer columns (including row_id, and one int64 column) plus 3 additional string or int columns (additional

Re: [sqlite] insert or ignore with foreign keys

> > I guess the example below shows the intended behaviour for Sqlite? > > PRAGMA FOREIGN_KEYS=1; > CREATE TABLE t1 ( > id INTEGER PRIMARY KEY > ); > > CREATE TABLE t2( > id INTEGER PRIMARY KEY, > t1_id INT NOT NULL, > CONSTRAINT fk FOREIGN KEY(t1_id) REFERENCES t1(id) > ); > > INSERT INTO t1

Re: [sqlite] insert or ignore with foreign keys

I think INSERT OR IGNORE is designed to insert a record into a table if a record with its primary key doesn't already exist. It's not an INSERT AND IGNORE ON ANY ERROR. So: INSERT OR IGNORE INTO t2 VALUES (1,1) INSERT OR IGNORE INTO t2 VALUES (1,1) The above would not cause an error where,