[sqlite] Crash bug in Sqlite

2019-12-19 Thread Yongheng Chen
Hi, We found another crash in Sqlite. Here’s the POC: — CREATE TABLE v0 ( v7 FLOAT , v3 DOUBLE , v6 TEXT , v1 INTEGER UNIQUE , v5 DOUBLE , v2 VARCHAR(20) UNIQUE , v4 ) ; REPLACE INTO v0 ( v6 , v3 , v2 ) VALUES ( 10 , 10 , 10 ); CREATE VIRTUAL TABLE v8 USING zipfile ( v9 DOUBLE ) ; REPLACE INTO

[sqlite] Query regarding Sqlite 3.30.1

2019-12-19 Thread Uthra Ganesan
Hi We are currently using SQLite 3.28.0. Can you please lt us know when can we expect 3.30.1 in Maven central repository. Thanks Uthra ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] Query regarding Sqlite 3.30.1

2019-12-19 Thread Richard Hipp
On 12/19/19, Uthra Ganesan wrote: > Hi > > We are currently using SQLite 3.28.0. Can you please lt us know when can we > expect 3.30.1 in Maven central repository. > Please ask whomever controls the "Maven central repository". They will make that determination, not us. -- D. Richard Hipp

Re: [sqlite] Crash bug in Sqlite

2019-12-19 Thread Jose Isaias Cabrera
Yongheng Chen, on Thursday, December 19, 2019 09:54 AM, wrote... > > Hi, > > We found another crash in Sqlite. Here’s the POC: > — > CREATE TABLE v0 ( v7 FLOAT , v3 DOUBLE , v6 TEXT , v1 INTEGER UNIQUE , v5 > DOUBLE , v2 VARCHAR(20) UNIQUE , v4 ) ; > REPLACE INTO v0 ( v6 , v3 , v2 ) VALUES ( 10 ,

[sqlite] Crash bug in Sqlite

2019-12-19 Thread Yongheng Chen
Hi, We found another crash in Sqlite. Here’s the POC: — CREATE TABLE v0 ( v1 INTEGER PRIMARY KEY ) ; CREATE VIEW v2 ( v3 ) AS SELECT DISTINCT ( SELECT DISTINCT v1 , v1 , v1 , v3 , v1 , v3 , v1 , 10.10 ) ; CREATE TABLE v4 ( v5 INTEGER PRIMARY KEY , v6 INT ); DELETE FROM v0 WHERE NULL BETWEEN

[sqlite] Crash Bug in Sqlite

2019-12-19 Thread Yongheng Chen
Hi, We found another crash in Sqlite. Here’s the POC: — CREATE TABLE v0 ( v1 , v2 ) ; SELECT 10 , 1 UNION SELECT v2 , dense_rank () OVER( ORDER BY - 10 ) FROM v0 ; — This bug exists in both the latest development code and the release code. Yongheng & Rui

Re: [sqlite] Crash Bug in Sqlite

2019-12-19 Thread Jose Isaias Cabrera
Yongheng Chen, on Thursday, December 19, 2019 04:29 PM, wrote... > > Hi, > > We found another crash in Sqlite. Here’s the POC: > — > CREATE TABLE v0 ( v1 , v2 ) ; > SELECT 10 , 1 UNION SELECT v2 , dense_rank () OVER( ORDER BY - 10 ) FROM > v0 ; > — > > This bug exists in both the latest

[sqlite] mysql -> sqlite problem

2019-12-19 Thread Mike Bentley
I used two different mysql to sqlite conversion tools to do test conversions. One tool is written in python and is called mysql-to-sqlite, and the other in awk called mysql2sqlite, both available via github. The one in python ran into an error and stopped very early in the process. The one

Re: [sqlite] Crash bug in Sqlite

2019-12-19 Thread Jose Isaias Cabrera
Yongheng Chen, on Thursday, December 19, 2019 01:21 PM, wrote... > > Hi, > > We found another crash in Sqlite. Here’s the POC: > — > CREATE TABLE v0 ( v1 INTEGER PRIMARY KEY ) ; > CREATE VIEW v2 ( v3 ) AS SELECT DISTINCT ( SELECT DISTINCT v1 , v1 , v1 , > v3 , v1 , v3 , v1 , 10.10 ) ; >

Re: [sqlite] mysql -> sqlite problem

2019-12-19 Thread Jens Alfke
> On Dec 19, 2019, at 4:49 PM, Mike Bentley wrote: > > Is it true that "Each index name must be unique in the database"? Yes. You're right that the docs don't seem to spell this out, but since the syntax to delete an index is "DROP INDEX ", you couldn't have multiple indexes with the same