On 3/2/20, Keith Medcalf wrote:
>
> Perhaps this is the same constant propagation bug that was fixed recently?
>
So it seems.
https://sqlite.org/src/timeline?bid=ya65c8d4e26n3bfa9cc97dn7d8dcfb95cy14d14eb537y109ee07433nabfb043ebbne0c6b8bdb7yc9a8defcef
--
D. Richard Hipp
d...@sqlite.org
Perhaps this is the same constant propagation bug that was fixed recently?
--
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users On
>Behalf Of Keith Medcalf
>Sent: Monday, 2 March,
No reproduco
SQLite version 3.32.0 2020-03-02 22:04:51
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> CREATE TABLE t (
...> textid TEXT
...> );
sqlite> INSERT INTO t
...> VALUES ('12');
sqlite
Right, Yinyue. Apologies. I actually thought I had built it. Thanks.
From: sqlite-users on behalf of
Xinyue Chen
Sent: Monday, March 2, 2020 06:40 PM
To: SQLite mailing list
Subject: Re: [sqlite] Report bug found in SQLite version 3.31.1
Hi josé,
This bu
Hi josé,
This bug is found in 3.31.1 but you are running it in 3.30.1.
Best,
Xinyue Chen
On Mon, Mar 2, 2020 at 3:36 PM Jose Isaias Cabrera
wrote:
> Xinyue Chen, on Monday, March 2, 2020 06:21 PM, wrote...
> >
> > Hi,
> >
> > I found a bug in the most recent SQLite release version 3.31.1
> 202
Xinyue Chen, on Monday, March 2, 2020 06:21 PM, wrote...
>
> Hi,
>
> I found a bug in the most recent SQLite release version 3.31.1 2020-01-27.
> My initial test environment is macOS 10.14.6 (18G87) and I have tested in
> https://sqliteonline.com/.
>
> CREATE TABLE t (
> textid TEXT
> );
> INSERT
Hi,
I found a bug in the most recent SQLite release version 3.31.1 2020-01-27.
My initial test environment is macOS 10.14.6 (18G87) and I have tested in
https://sqliteonline.com/.
CREATE TABLE t (
textid TEXT
);
INSERT INTO t
VALUES ('12');
INSERT INTO t
VALUES ('34');
CREATE TABLE i (
intid
On Monday, 2 March, 2020 09:20, Dominique Devienne wrote:
>On Mon, Mar 2, 2020 at 5:09 PM Keith Medcalf wrote:
>> select group_concat(value) from (select distinct value from test order by
>> value);
>But is that guaranteed to be ordered correctly "forever" instead of by
>"happenstance" from
On Mon, Mar 2, 2020 at 5:09 PM Keith Medcalf wrote:
> select group_concat(value) from (select distinct value from test order by
> value);
But is that guaranteed to be ordered correctly "forever" instead of by
"happenstance"
from current implementation details? My point was that the Window
Functi
Thanks Jens and everyone. I'll try the approach of compiling statements on
the fly.
Best wishes,
Hamish
On Sat, 29 Feb 2020 at 23:13, Jens Alfke wrote:
>
> > On Feb 28, 2020, at 11:49 PM, Hamish Allan wrote:
> >
> > Again, I may be making incorrect assumptions.
>
> Remember the old Knuth quot
You mean like:
select group_concat(value) over (order by value rows between unbounded
preceding and unbounded following) from (select distinct value from test) limit
1;
and
select group_concat(value) over (order by value desc rows between unbounded
preceding and unbounded following) from (sele
On Sun, Mar 1, 2020 at 10:58 PM mailing lists wrote:
> Are there any other solutions / possibilities?
I thought someone more knowledgeable than I about Window Functions [1]
would answer,
but since nobody mentioned them so far, I'll do it, as I believe this
is the "SQL native" way
to achieve what
On 1/03/2020 22:57, mailing lists wrote:
Assume I create the following table:
CREATE TABLE Test (ID INTEGER PRIMARY KEY, Value TEXT);
INSERT INTO Test (Value) VALUES('Alpha');
INSERT INTO Test (Value) VALUES('Beta');
INSERT INTO Test (Value) VALUES('Beta');
INSERT INTO Test (Value) VALUES('Alpha
Hi Keith,
thanks for the explanation.
PS: I used a CTE because official examples (e.g. Mandelbrot) also used CTEs in
combination with group_concat. Although the incorporation of group_concat was
not the primary reason to use CTEs.
PPS: Is it possible to rephrase the documentation for group_conc
14 matches
Mail list logo