On 2016/04/19 8:34 PM, Jarred Ford wrote:
> Is it possible to create multiple in-memory databases and be able to access
> tables with a single query between them? For example, select * from
> db1.dbo.table1 db1 join db2.dbo.table1 db2 on db1.x = db2.x.
No. An in-memory database has no
On 4/19/16, Nikos Tsikoudis wrote:
> On 4/19/2016 8:25 PM, Richard Hipp wrote:
>> https://www.sqlite.org/c3ref/interrupt.html
>>
>> Or have your function throw an error using sqlite3_result_error() -
>> https://www.sqlite.org/c3ref/result_blob.html
>>
> That works but in the function I update
On 4/19/2016 8:25 PM, Richard Hipp wrote:
> On 4/19/16, Nikolaos Tsikoudis wrote:
>> Hi,
>>
>> I'm wondering if there is a way to stop the query I execute in a SQL
>> Function, the one you create by using the sqlite3_create_function
>> functions.I
>> have created a SQL function which is called
On Apr 19, 2016, at 1:34 PM, Jarred Ford wrote:
> Is it possible to create multiple in-memory databases and be able to access
> tables with a single query between them?
> For example, select * from db1.dbo.table1 db1 join db2.dbo.table1 db2 on
> db1.x = db2.x.
>
Sure. Like any other
On 4/19/16, Nikolaos Tsikoudis wrote:
> Hi,
>
> I'm wondering if there is a way to stop the query I execute in a SQL
> Function, the one you create by using the sqlite3_create_function
> functions.I
> have created a SQL function which is called for every tuple returned by my
> queries and I would
Hi,
I'm wondering if there is a way to stop the query I execute in a SQL
Function, the one you create by using the sqlite3_create_function functions.I
have created a SQL function which is called for every tuple returned by my
queries and I would like the query to stop when a statement in the
Hello,
I got this error "sqlite3.OperationalError: database or disk is full? and I
researched about it and created another directory that has lot of space and
pointed SQLITE_TMPDIR, TMPDIR, TMP, TEMP to the newly created directory. I also
used sqlitecur.execute("PRAGMA temp_store = 1;?) but it
Is it possible to create multiple in-memory databases and be able to access
tables with a single query between them? For example, select * from
db1.dbo.table1 db1 join db2.dbo.table1 db2 on db1.x = db2.x.
Thanks.
2016-04-19 15:29 GMT+02:00 R Smith :
>
>
> On 2016/04/19 2:49 PM, Cecil Westerhof wrote:
>
>> 2016-04-18 12:47 GMT+02:00 Olivier Mascia :
>>
>> PRAGMA compile_options; (has SQLITE_SECURE_DELETE been set for compiling
>>> the library?)
>>>
>>> ?sqlite3 checkUUID.sqlite
>> SQLite version 3.8.7.1
2016-04-19 15:27 GMT+02:00 Olivier Mascia :
> > Le 19 avr. 2016 ? 14:49, Cecil Westerhof a
> ?crit :
> >
> > SECURE_DELETE
>
> Are you aware of the net effect of SQLITE_SECURE_DELETE?
>
> https://www.sqlite.org/compile.html#secure_delete
>
> The documentation talks about a "small performance
2016-04-19 15:12 GMT+02:00 Simon Slavin :
>
> On 19 Apr 2016, at 1:49pm, Cecil Westerhof wrote:
>
> > ?Is it not strange that first DELETE and then DROP is so more efficient
> as
> > just a DROP?
>
> Yes.
>
> Can you please try the same comparison in the SQLite shell tool ? You can
> use
>
>
On 2016/04/19 2:49 PM, Cecil Westerhof wrote:
> 2016-04-18 12:47 GMT+02:00 Olivier Mascia :
>
>> PRAGMA compile_options; (has SQLITE_SECURE_DELETE been set for compiling
>> the library?)
>>
> ?sqlite3 checkUUID.sqlite
> SQLite version 3.8.7.1 2014-10-29 13:59:56
> Enter ".help" for usage hints.
> Le 19 avr. 2016 ? 14:49, Cecil Westerhof a ?crit :
>
> SECURE_DELETE
Are you aware of the net effect of SQLITE_SECURE_DELETE?
https://www.sqlite.org/compile.html#secure_delete
The documentation talks about a "small performance penalty", yet on very large
tables, especially if overflowing
2016-04-19 4:43 GMT+02:00 Rowan Worth :
> On 19 April 2016 at 02:01, Cecil Westerhof wrote:
>
> > 2016-04-18 4:04 GMT+02:00 Rowan Worth :
> >
> > > On 18 April 2016 at 06:55, Cecil Westerhof
> > wrote:
> > >
> > > > ?I put a strace on it. This was what I got:
> > > > Process 26455 attached with
2016-04-18 12:47 GMT+02:00 Olivier Mascia :
> PRAGMA compile_options; (has SQLITE_SECURE_DELETE been set for compiling
> the library?)
>
?sqlite3 checkUUID.sqlite
SQLite version 3.8.7.1 2014-10-29 13:59:56
Enter ".help" for usage hints.
sqlite> PRAGMA compile_options;
ENABLE_COLUMN_METADATA
On 19 Apr 2016, at 1:49pm, Cecil Westerhof wrote:
> ?Is it not strange that first DELETE and then DROP is so more efficient as
> just a DROP?
Yes.
Can you please try the same comparison in the SQLite shell tool ? You can use
.timer ON
DELETE FROM myTable;
DROP TABLE myTable;
.timer OFF
> On Thu, 31 Mar 2016 10:21:53 -0400
> Richard Hipp wrote:
>
>> On 3/31/16, Kristaps Dzonsons wrote:
>>>
>>> Is there any interest in integrating this tool to have manpages in
>>> the doc distribution without downstream bits?
>>>
>>
>> I think that would be cool. Integrating your tool into the
On 19 April 2016 at 02:01, Cecil Westerhof wrote:
> 2016-04-18 4:04 GMT+02:00 Rowan Worth :
>
> > On 18 April 2016 at 06:55, Cecil Westerhof
> wrote:
> >
> > > ?I put a strace on it. This was what I got:
> > > Process 26455 attached with 20 threads
> > > % time seconds usecs/call calls
System.Data.SQLite version 1.0.101.0 (with SQLite 3.12.2) is now available
on the System.Data.SQLite website:
https://system.data.sqlite.org/
Further information about this release can be seen at:
https://system.data.sqlite.org/index.html/doc/trunk/www/news.wiki
Please post on the
Hi,
Gesendet:?Montag, 18. April 2016 um 19:38 Uhr
Von:?"Richard Hipp"
> On 4/18/16, Clemens Ladisch wrote:
> >
> > Quoting an indentifier prevents the database from interpreting it as a
> > keyword.
> >
> > Arguably, the old SQLite version did this wrong in this case.
>
> Backwards
On 4/18/2016 6:46 AM, Paul Sanderson wrote:
> You could use a binary PList or some other form of structured data -
> the BPList blob could then contain, ints, floats, strings byte arrays
> or even embedded binary plists. As it is a structured format then to
> an extent it is self documenting (in
21 matches
Mail list logo
