On 5 Jan 2020, at 5:01pm, Amer Neely wrote:
> But the question still remains, why the different results?
The optimizer gets improved from time to time in SQLite versions. SQLite
solved the problem faster by breaking down your query differently: deciding
whether to do one scan or use two index
> On Saturday, 4 January, 2020 18:31, Amer Neely
> wrote:
>
>> I'm fairly new to SQLite, but have been using MySQL / mariadb in a local
>> and web-based environment for several years. So far I'm happy and
>> impressed with SQLite, but I recently noticed some odd behaviour with
>> one of my querie
-- > What is your version of Perl and the SQLite module?
This is perl 5, version 18, subversion 2 (v5.18.2) built for
darwin-thread-multi-2level
(with 2 registered patches, see perl -V for more detail)
Copyright 1987-2013, Larry Wall
SQLite version 3.30.1 2019-10-10 20:19:45
Enter ".help" for u
--
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
On Saturday, 4 January, 2020 18:31, Amer Neely wrote:
>I'm fairly new to SQLite, but have been using MySQL / mariadb in a local
>and web-based environment for several years
Hi,
On Sat, Jan 4, 2020 at 7:31 PM Amer Neely wrote:
>
> Hello all,
> I'm fairly new to SQLite, but have been using MySQL / mariadb in a local
> and web-based environment for several years. So far I'm happy and
> impressed with SQLite, but I recently noticed some odd behaviour with
> one of my qu
Hello all,
I'm fairly new to SQLite, but have been using MySQL / mariadb in a local
and web-based environment for several years. So far I'm happy and
impressed with SQLite, but I recently noticed some odd behaviour with
one of my queries.
Using the command-line in a shell (Mac High Sierra) I get a
6 matches
Mail list logo