>
> Op 17 sep. 2019, om 04:26 heeft Keith Medcalf het
> volgende geschreven:
>
>
> On Monday, 16 September, 2019 14:22, E.Pasma wrote:
>
>> Stop stop stop
>
> You are right. What a difference a spelling error makes ... No wonder it
> took so long as it was doing table scans -- and the opt
. And continues as if
zero is passed in. This way a WHERE condition like
=
can be true. Regular tables require "IS" instead of "=" here.
Theoretically the left join reduction prover can now be misleaded. As
is the case below,
Is this a (obscure) bug in generate_series
c.
If you reduce the number of anticipated levels, by leaving out the
last four lines, the output is alright.
Hope this causes no headache, E. Pasma
.version
SQLite 3.23.0 2018-03-22 12:00:43
dd568c27b1d7656388ea5b4132cc0265aedd7348d265d8e8c7412b00b28a31aa
zlib version 1.2.3
gcc-4.0.1 (Appl
has a full scan on t2 instead of direct access
via the existing index sqlite_autoindex_t2_1. The view is apparently
not flattened. Is it possible changing this? Thanks, E. Pasma
.version
SQLite 3.21.0 2017-10-02 02:52:54
c9104b59c7ed360291f7f6fc8caae938e9840c77620d598e4096f78183bf807a
Keith, this definitely explains the observed time as it is relative to
count(a)*count (ab)**2, thus non-linear.
And a correlated sub-query is generally recalculated for each row.
But I do not agree with everything.
In my example it is correlated to the outermost query, and not to the
sub-que
row 1')
;
It is alright after changing the order in the multiple values. Hope
I'm not mistaken.Thanks, E. Pasma
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
c and sqlite3_free
instead of the C primitives.
2. is it imaginable to obtain the same functionality without a C
extension, by using plain replace() inside a recursive CTE?
Thanks, E. Pasma
.load ./sqlite3_group_replace_extension
create table kv (k, v, reverse);
insert into kv values ('1
Hello,
this mail is about the aggregate feature that was unveiled in the
release log of version 3.17.11, http://www.sqlite.org/releaselog/3_7_11.html
:
A query of the form: "SELECT max(x), y FROM table" returns the value
of y on the same row that contains the maximum x value.
I just wan
Op 2-jan-2010, om 9:32 heeft Roger Binns het volgende geschreven:
> Darren Duncan wrote:
>> I would like to bring an apparent SQLite bug to the attention of
>> the SQLite core
>> developers as a ticket, where build fails on sun4-solaris-64int 2.10
>
> You'll find this is not a bug in SQLite.
>
>
9 matches
Mail list logo