Hi,
We found a assertion bug in sqlite3, here is the poc:
—
CREATE TABLE v0 ( v1 CHAR(25) , v2 INTEGER UNIQUE ON CONFLICT ABORT NOT NULL
PRIMARY KEY CHECK( datetime ( lower ( v2 ) , NOT lower ( v1 / 1 ) ) == 'MED
PACK' NOT LIKE v2 ) ) ; CREATE TRIGGER alias AFTER INSERT ON v0 BEGIN INSERT OR
ry
error.
Thanks,
Ming Jia
> On Dec 27, 2019, at 2:56 PM, Keith Medcalf wrote:
>
>
> On Friday, 27 December, 2019 12:50, Igor Korot wrote:
>
>> On Fri, Dec 27, 2019 at 12:57 PM Bigthing Do wrote:
>
>>> We met an accidental crash in sqlite with the following
Hi Manuel,
Hh, what a coincident. It might be so. The test case looks very different
though. Let’s wait for Richard to find it out then.
Yongheng & Rui
> On Dec 27, 2019, at 2:03 PM, Manuel Rigger wrote:
>
> Hi Yongheng and Rui,
>
> This might be a duplicate to a bug that I reported, since
Dear sqlite developers:
We met an accidental crash in sqlite with the following sample:
CREATE VIEW table1 ( col1 , col2 ) AS WITH aaa AS ( SELECT * FROM table1 )
SELECT col2 FROM table1 ORDER BY 1 ;
WITH aaa AS ( SELECT * FROM table1 ) SELECT col1 , rank () OVER( ORDER BY col1
DESC ) FROM
4 matches
Mail list logo