On Thu, 30 Nov 2017, Vladimir Marek wrote:
Hi,
Compilers shipped with Solaris were traditionally compiling 32bit
binaries unless specified otherwise. This changed recently, the default
is 64bit binaries. So if you want to compile 32bit object, you have to
specify -m32. That slightly breaks
Thanks for reporting this. Now fixed here:
http://www.sqlite.org/src/info/5771b1d611b3562e
Dan.
On 12/01/2017 02:02 AM, David Raymond wrote:
I’m using the CLI’s .lint fkey-indexes command, and it appears to be having
issues with without rowid tables. A low priority thing to look into
> Le 1 déc. 2017 à 15:00, Clemens Ladisch <clem...@ladisch.de> a écrit :
>
> Olivier Mascia wrote:
>> 20171201 120319.404 284: automatic index on REMINDER(USER_LOGON)
>>
>> Here is that part of the schema:
>>
>> CREATE INDEX IX_REMIND
> Le 1 déc. 2017 à 14:58, Clemens Ladisch a écrit :
>
> Olivier Mascia wrote:
>> I'm seeing such things in my error.log out of SQLite 3.21.0 (but I am sure
>> it was already the case with 3.20):
>>
>> automatic index on tal(ID)
>> automatic index on mi(ID)
>> ...
>>
>> I
to close this subject I have some more information.
After a try on my ubuntu I notice that the différence doesn't exist. So I
ugraded the production HOST to à 4.4 linux kernel.
The timing is now the same on the host and in the container ( but both are
slower. snif ... )
fs tuning is not so
On 1 Dec 2017, at 1:50pm, Olivier Mascia wrote:
> Could it be that it might need a DESC index?
SQLite should not be doing that. It understands that an index can be used
"backwards" if it needs to reverse the sort order.
> Could the "automatic index on ..." in the error
the logs? That should make it
clear and is much better info than the logging provides.
On 2017/12/01 3:50 PM, Olivier Mascia wrote:
Hi all,
I'm also seeing such things in my SQLite log:
20171201 120319.404 284: automatic index on REMINDER(USER_LOGON)
20171201 120319.404 284: automatic index
Olivier Mascia wrote:
> 20171201 120319.404 284: automatic index on REMINDER(USER_LOGON)
>
> Here is that part of the schema:
>
> CREATE INDEX IX_REMINDER_USER on REMINDER(USER_LOGON);
>
> Could it be that it might need a DESC index?
Probably not; the index direction us
Olivier Mascia wrote:
> I'm seeing such things in my error.log out of SQLite 3.21.0 (but I am sure it
> was already the case with 3.20):
>
> automatic index on tal(ID)
> automatic index on mi(ID)
> ...
>
> I do not have a clue as to what these 'tal(ID)' and 'mi(ID)' refer to.
"tal" and "mi"
Hi all,
I'm also seeing such things in my SQLite log:
20171201 120319.404 284: automatic index on REMINDER(USER_LOGON)
20171201 120319.404 284: automatic index on REMINDER(USER_LOGON)
20171201 120326.763 284: automatic index on REMINDER(USER_LOGON)
20171201 120326.763 284: automatic index
Hi all,
I'm seeing such things in my error.log out of SQLite 3.21.0 (but I am sure it
was already the case with 3.20):
automatic index on tal(ID)
automatic index on mi(ID)
automatic index on tal(ID)
automatic index on mi(ID)
automatic index on mi(ID)
automatic index on mi(ID)
automatic index on
On Wed Nov 29, 2017 at 01:57:29PM +, David Raymond wrote:
> http://www.sqlite.org/compile.html
>
> SQLITE_ENABLE_UNKNOWN_SQL_FUNCTION
Exactly what I was looking for, just in the wrong places. Thanks David.
--
Mark Lawrence
___
sqlite-users
12 matches
Mail list logo