On 11/09/2017 08:59 AM, advancenOO wrote:
I am trying to understand how SQLITE_DEFAULT_MMAP_SIZE works and I think db
files can use MMAP by using this compilation option, as Sqlite3PagerGet()
mapped to getPageMMap().
And I know "/the current VFS implementations use a mmapped file for the
I am trying to understand how SQLITE_DEFAULT_MMAP_SIZE works and I think db
files can use MMAP by using this compilation option, as Sqlite3PagerGet()
mapped to getPageMMap().
And I know "/the current VFS implementations use a mmapped file for the
wal-index/"
But is there a way that wal-files
On 11/8/17, korablev wrote:
> What is the timeline of this feature? Will it be implemented in the nearest
> future?
Low priority. I do not like automatic index feature, because I think
that app developers should do an appropriate CREATE INDEX instead. Of
course, it is not
What is the timeline of this feature? Will it be implemented in the nearest
future? And what optimizations doesn't also work on without rowid tables? Is
the query planner good at optimizing stuff on without rowid tables at all?
--
Sent from: http://sqlite.1065341.n5.nabble.com/
Thank you all! I really have to do a thorough read of all the pragmas,
there are so many useful things in there! The user version sounds exactly
like what I should be using for storing the db version, and presumably the
data_version is a little faster still than reading the user version.
@Keith,
On 11/8/17, Jens Alfke wrote:
> Is it possible for a user-defined function to determine the collation
> associated with its argument(s)? I'm implementing some custom string
> matching/comparison functions, and I want their case-sensitivity to depend
> on the collation of the
Is it possible for a user-defined function to determine the collation
associated with its argument(s)? I'm implementing some custom string
matching/comparison functions, and I want their case-sensitivity to depend on
the collation of the first argument (the LHS).
I’ve searched sqlite3.h for
On 11/8/17, Richard Hipp wrote:
>
> Expect to see fresh precompiled binaries that fix this problem within
> a few hours.
>
New builds for the "sqlite-tools-*-321.zip" packages are now
available from the https://sqlite.org/download.html webpage
--
D. Richard Hipp
On 11/8/17, Peter Da Silva wrote:
> On 11/8/17, 8:20 AM, "sqlite-users on behalf of Richard Hipp"
>
> wrote:
>> The technical reason for this is that, from the point of view of the query
>>
On 11/8/17, Klaas Van B. wrote:
> In 3.20.1 the dot-command dbinfo still worked, but since 3.21.0 not anymore
This was a boo-boo on our precompiled-binary build script. The
".dbinfo" command was modified to require a special compile-time
option (specifically
On 11/8/17, 8:20 AM, "sqlite-users on behalf of Richard Hipp"
wrote:
> The technical reason for this is that, from the point of view of the query
> planner, a WITHOUT ROWID table is really a covering index
So basically
On 11/8/17, korablev wrote:
> sqlite> create table t1(a primary key, b) without rowid;
> sqlite> create table t2(a primary key, b) without rowid;
> sqlite> explain query plan select * from t1, t2 where t1.b = t2.b;
> 0|0|0|SCAN TABLE t1
> 0|1|1|SCAN TABLE t2
> sqlite> create
In 3.20.1 the dot-command dbinfo still worked, but since 3.21.0 not anymore
sqlite32001 e0.sqb
SQLite version 3.20.1 2017-08-24 16:21:36
Enter ".help" for usage hints.
sqlite> .dbinfo
database page size: 512
write format: 1
read format: 1
reserved bytes: 0
file change counter:
On 11/08/2017 03:55 PM, Dominique Devienne wrote:
On Wed, Nov 8, 2017 at 7:45 AM, Dan Kennedy wrote:
On 7 Nov 2017, at 6:53pm, David Raymond wrote:
I think pragma data_version is what you're looking for.
On Wed, Nov 8, 2017 at 7:45 AM, Dan Kennedy wrote:
> On 7 Nov 2017, at 6:53pm, David Raymond wrote:
>>
>> I think pragma data_version is what you're looking for.
>>> http://www.sqlite.org/pragma.html#pragma_data_version
>>>
>>
> I think it's the
15 matches
Mail list logo