Roger Binns wrote [on Sun, 03 Jan 2010 09:56:46 -0800]:
> Adam Kennedy wrote:
>> Unfortunately, we neither have the ability to run configure (as we
>> don't have reliable access to /bin/sh or any of the other stuff it
>> needs) or the ability to use a pregenerated static configuration
>> across
On Jan 5, 2010, at 6:25 AM, Noah Hart wrote:
> Using the command line tools from the website
> 3.6.18 reports the error correctly;
>
> SQLite version 3.6.18
> sqlite> PRAGMA recursive_triggers = on;
> sqlite> CREATE TABLE t5 (a primary key, b, c);
> sqlite> INSERT INTO t5 values (1, 2, 3);
>
Using the command line tools from the website
3.6.18 reports the error correctly;
SQLite version 3.6.18
sqlite> PRAGMA recursive_triggers = on;
sqlite> CREATE TABLE t5 (a primary key, b, c);
sqlite> INSERT INTO t5 values (1, 2, 3);
sqlite> CREATE TRIGGER au_tbl AFTER UPDATE ON t5 BEGIN UPDATE OR
Between versions 3.6.19 and 3.6.20 something has changed
which causes the command line tool to ignore the .echo ON
command for some statements.
CREATE and INSERT statements aren't echoed anymore,
but SELECT statements are echoed correctly.
Needless to say that this makes it a bit harder to
Jeremy Zeiber wrote:
> SELECT headerid,
> (SELECT COUNT(data) FROM detail AS outerdetail WHERE
> headerid=header.headerid AND data NOT IN (SELECT DISTINCT data FROM
> detail WHERE headerid FROM header GROUP BY headerid;
Try this:
select
If you were wanting to copy all of the in-memory database tables to a
file, rather than just one, then the backup api might be another way to
go.
http://www.sqlite.org/backup.html
(I haven't used it myself but the documentation lists copying from
memory database instances to file databases as
On Jan 4, 2010, at 6:35 AM, sasikuma...@tcs.com wrote:
> I'm using SQLite DB version 3.6.12. I recently read about the feature of
> In-Memory Database and tried to implement it. I was able to create a new
> DB connection in memory, able to create a table and insert some set of
> records into
On 4 Jan 2010, at 3:44pm, Jeremy Zeiber wrote:
> Believe it or not, these indexes made the query run the fastest:
> CREATE UNIQUE INDEX idx1 ON detail(headerid,data);
> CREATE UNIQUE INDEX idx2 ON detail(data,headerid);
That makes perfect sense since your SELECT command does require sorting by
On Jan 4, 2010, at 10:36 AM, Olivier Roger wrote:
> Hello,
> for some project we need an encryption on our database. SQLite
> Encryption Extension seems to fit our need perfectly but some
> questions
> remain.
>
> After having paid the license fee we can download the entire source
> code
>
Simon Slavin wrote:
> On 4 Jan 2010, at 3:02pm, Simon Davies wrote:
>
>
>> 2010/1/4 Simon Slavin :
>>
>>> On 4 Jan 2010, at 2:38pm, Jeremy Zeiber wrote:
>>>
>>>
SELECT headerid,
(SELECT (SELECT COUNT(DISTINCT data) FROM detail WHERE
Hello,
for some project we need an encryption on our database. SQLite
Encryption Extension seems to fit our need perfectly but some questions
remain.
After having paid the license fee we can download the entire source code
of the extension, right ? not only a dll (or equivalent)
The encrypted
Simon Davies wrote:
> 2010/1/4 Simon Slavin :
>
>> On 4 Jan 2010, at 2:38pm, Jeremy Zeiber wrote:
>>
>>
>>> That particular query runs in ~ 30 seconds with outerdetail.header or
>>> header.headerid. I do have another query which gives the same result
>>> that doesn't
On 4 Jan 2010, at 3:02pm, Simon Davies wrote:
> 2010/1/4 Simon Slavin :
>>
>> On 4 Jan 2010, at 2:38pm, Jeremy Zeiber wrote:
>>
>>> SELECT headerid,
>>> (SELECT (SELECT COUNT(DISTINCT data) FROM detail WHERE
>>> headerid=header.headerid)-COUNT(DISTINCT one.data) FROM
2010/1/4 Simon Slavin :
>
> On 4 Jan 2010, at 2:38pm, Jeremy Zeiber wrote:
>
>> That particular query runs in ~ 30 seconds with outerdetail.header or
>> header.headerid. I do have another query which gives the same result
>> that doesn't quite run as fast as the first, but
On 4 Jan 2010, at 2:38pm, Jeremy Zeiber wrote:
> That particular query runs in ~ 30 seconds with outerdetail.header or
> header.headerid. I do have another query which gives the same result
> that doesn't quite run as fast as the first, but it is certainly faster
> than the second:
>
>
Igor Tandetnik wrote:
> Jeremy Zeiber wrote:
>
>> This query runs in ~ 17 ms:
>> SELECT COUNT(data) FROM detail AS outerdetail WHERE headerid=4 AND data
>> NOT IN (SELECT DISTINCT data FROM detail WHERE headerid<4)
>>
>
> Here the subquery is not coordinated. It is run once, the results
I noticed that setting temp_store to DISK surprisingly improved the
performance in some cases comparing to the same operation when it was set to
MEMORY. Looking at the numbers I noticed that in case of MEMORY one
operation that actually does select spread over a large table always led to
big data
Summary:
* At the very least a documentation change is needed on the subject
of the errno value from disk i/o errors.
* Ticket #2398 (on the subject of EINTR) should probably be reopened.
I have recently had an apparently isolated failure of a program making
some updates to a sqlite
sasikuma...@tcs.com wrote:
> I'm using SQLite DB version 3.6.12. I recently read about the feature of
> In-Memory Database and tried to implement it. I was able to create a new
> DB connection in memory, able to create a table and insert some set of
> records into the memory DB.
>
> How should I
On 4 Jan 2010, at 11:35am, sasikuma...@tcs.com wrote:
> I'm using SQLite DB version 3.6.12. I recently read about the feature of
> In-Memory Database and tried to implement it. I was able to create a new
> DB connection in memory, able to create a table and insert some set of
> records into
Hi All,
I'm using SQLite DB version 3.6.12. I recently read about the feature of
In-Memory Database and tried to implement it. I was able to create a new
DB connection in memory, able to create a table and insert some set of
records into the memory DB.
How should I now transfer those records
21 matches
Mail list logo