On 4 May 2017 at 01:16, Olivier Mascia wrote:
> > Le 3 mai 2017 à 18:46, Richard Hipp a écrit :
> >
> > On 5/3/17, Olivier Mascia wrote:
> >> automatic index on sqlite_sq_25FA4563E0(ID) (284)
> >> ...
> >>
> >> I guess they mean
> Le 3 mai 2017 à 19:44, Tim Streater a écrit :
>
>> Would there be a cheap way for SQLite to log some more user-realm context
>> about these?
>> Maybe simply emitting a second call to the log function right after these
>> messages code 284 where the third parameter (msg)
On 3 May 2017, at 18:16, Olivier Mascia wrote:
> Would there be a cheap way for SQLite to log some more user-realm context
> about these?
> Maybe simply emitting a second call to the log function right after these
> messages code 284 where the third parameter (msg) would simply
> Le 3 mai 2017 à 18:46, Richard Hipp a écrit :
>
> On 5/3/17, Olivier Mascia wrote:
>> automatic index on sqlite_sq_25FA4563E0(ID) (284)
>> ...
>>
>> I guess they mean SQLite decided to build some temporary index for some
>> query execution, just
On 5/3/17, Olivier Mascia wrote:
> automatic index on sqlite_sq_25FA4563E0(ID) (284)
> ...
>
> I guess they mean SQLite decided to build some temporary index for some
> query execution, just as for the first case. But here the table itself looks
> like internal and
Dear,
On such a log line as:
automatic index on REMINDER(USER_LOGON) (284)
I understand what it means and what I might want to do (or not).
Though what should I understand from line like these:
automatic index on sqlite_sq_25FA456860(ID) (284)
automatic index on
6 matches
Mail list logo