Re: [sqlite] [EXTERNAL] xRowid and read only virtual tables....

2017-10-17 Thread dave
> -Original Message- > From: sqlite-users > [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On > Behalf Of Hick Gunter > > In our virtual table implementations, we are using the rowid > to return the location of the record in the backing store > (e.g. record offset in the file

Re: [sqlite] [EXTERNAL] xRowid and read only virtual tables....

2017-10-17 Thread dave
> Behalf Of Dan Kennedy > Sent: Tuesday, October 17, 2017 11:58 AM > > On 10/17/2017 01:22 PM, Hick Gunter wrote: > > In our virtual table implementations, we are using the > rowid to return the location of the record in the backing > store (e.g. record offset in the file used as a backing >

[sqlite] System.Data.SQLite version 1.0.106.0 pre-release packages now available

2017-10-17 Thread Joe Mistachkin
Pre-release packages of System.Data.SQLite version 1.0.106.0 are now available on the System.Data.SQLite website: https://system.data.sqlite.org/ Please click on the "Pre-Release Download" link in order to view the available pre-release packages. Further information about this upcoming

Re: [sqlite] [EXTERNAL] xRowid and read only virtual tables....

2017-10-17 Thread Dan Kennedy
On 10/17/2017 01:22 PM, Hick Gunter wrote: In our virtual table implementations, we are using the rowid to return the location of the record in the backing store (e.g. record offset in the file used as a backing store, offset within a shared memory section or maybe even the memory address of

Re: [sqlite] xRowid and read only virtual tables....

2017-10-17 Thread dave
> On 10/16/17, dave wrote: > > Hi, I am building a system which involves a number of virtual table > > implementations. They are all read-only, but will be > involved in a bunch of > > joins amongst themselves. My question is this: > > > > the documentation > >

Re: [sqlite] Sqlite3.6 Command-line delete/update not working with large db file(>280GB)

2017-10-17 Thread David Raymond
If you're doing 1 gigantic insert to populate the table then it's more efficient to delay creating an index until the end. If you've already got a bunch of data in there and are inserting more, then you get diminishing returns from that. In this case though you're not creating a separate good

Re: [sqlite] Using .testcase and .check in continuous integration test

2017-10-17 Thread Dominique Devienne
On Tue, Oct 17, 2017 at 3:16 PM, Lodewijk Duymaer van Twist < lodew...@adesys.nl> wrote: > Thank you for investigating. You're fix works. Should I repost this as a > bug with your fix, or will this be picked up as is right now? > Glad it did. Just sit tight and again wait and see if Dr Hipp

Re: [sqlite] Using .testcase and .check in continuous integration test

2017-10-17 Thread Lodewijk Duymaer van Twist
Hi Dominique, Thank you for investigating. You're fix works. Should I repost this as a bug with your fix, or will this be picked up as is right now? Kind regard, Lodewijk Van: "Dominique Devienne" Aan: "sqlite-users"

Re: [sqlite] Using .testcase and .check in continuous integration test

2017-10-17 Thread Dominique Devienne
On Tue, Oct 17, 2017 at 12:30 PM, Lodewijk Duymaer van Twist < lodew...@adesys.nl> wrote: > That would be an other way, but what I'm looking for is using the Command > Line Shell ".testcase" and ".check" method. > OK. That's new information :) > Create an example test file: > echo ".testcase

Re: [sqlite] xRowid and read only virtual tables....

2017-10-17 Thread Richard Hipp
On 10/16/17, dave wrote: > Hi, I am building a system which involves a number of virtual table > implementations. They are all read-only, but will be involved in a bunch of > joins amongst themselves. My question is this: > > the documentation >

Re: [sqlite] Using .testcase and .check in continuous integration test

2017-10-17 Thread Lodewijk Duymaer van Twist
Hi Dominique, That would be an other way, but what I'm looking for is using the Command Line Shell ".testcase" and ".check" method. Create an example test file: echo ".testcase 100 SELECT (1,2,3)<(1,2,4), (1,2,3)<(1,NULL,4), (1,2,3)<(2,NULL,1); .check 1||1 .testcase 110 SELECT

[sqlite] Performance issue for version 3.9.2 compared with 3.16.2

2017-10-17 Thread advancenOO
In order to profile sqlite 3.9.2 and sqlite 3.16.2, I run speedtest1.c on my mobile phone. It is weird to find that 3.9.2 is better than 3.16.2, especially in the following case: “270, 1 DELETEs, numeric BETWEEN, indexed" 3.9.2 uses 0.7s while 3.16.2 uses 1.8s; My relevant

Re: [sqlite] [EXTERNAL] current_timestamp locale

2017-10-17 Thread Stephen Chrzanowski
Yes, I understand that beyond integer, float, and chars, there are no further "types", but I was just questioning whether current_timestamp formats what it stores in a specific manor, or, if it has some dealings with the locale of the system its executed on. You've answered the question. Thanks.

Re: [sqlite] [EXTERNAL] one to one relationships

2017-10-17 Thread Hick Gunter
What is the question? -Ursprüngliche Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Paul Alagna Gesendet: Dienstag, 17. Oktober 2017 08:35 An: sqlite-users@mailinglists.sqlite.org Betreff: [EXTERNAL] [sqlite] one to one relationships 2

Re: [sqlite] [EXTERNAL] current_timestamp locale

2017-10-17 Thread Hick Gunter
There is no "DATE" type in SQLite. The current_timestamp is a TEXT value equivalent to datetime('now') which returns an ISO formatted datetime string in UTC (-MM-DD HH:MM:SS). -Ursprüngliche Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im

[sqlite] one to one relationships

2017-10-17 Thread Paul Alagna
2 tables keyed alike are in a one to one relationship. IE every record of T1 will yield one and only one record in T2 PAUL ALAGNA pjala...@gmail.com ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] [EXTERNAL] xRowid and read only virtual tables....

2017-10-17 Thread Hick Gunter
In our virtual table implementations, we are using the rowid to return the location of the record in the backing store (e.g. record offset in the file used as a backing store, offset within a shared memory section or maybe even the memory address of the record image) and also implement fast