The bug does not exist in any released version of SQLite. It only
appears in unreleased development versions.
On 12/15/19, Chris Brody wrote:
>> Yes. I discovered the same thing independently. The previous fix was
>> subtly wrong. Please try the latest trunk version.
>
> Will there be a
> Yes. I discovered the same thing independently. The previous fix was
> subtly wrong. Please try the latest trunk version.
Will there be a patch release, or should we just wait for the next minor?
___
sqlite-users mailing list
On 12/9/19, Rui Zhong wrote:
> I tried in latest trunk version which check in
> commit 926f796e8feec15f3836aa0a060ed906f8ae04d3 and it crashed.
> I did not see any more recent commit in GITHUB. Could you please
> double check it?
GitHub is a mirror. The mirror is updated about once per hour.
I tried in latest trunk version which check in
commit 926f796e8feec15f3836aa0a060ed906f8ae04d3 and it crashed.
I did not see any more recent commit in GITHUB. Could you please
double check it?
Richard Hipp 于2019年12月9日周一 下午1:23写道：
> On 12/9/19, Rui Zhong wrote:
> > Hi,
> > We found this bug
On 12/9/19, Rui Zhong wrote:
> Hi,
> We found this bug can be triggered again after fix.
Yes. I discovered the same thing independently. The previous fix was
subtly wrong. Please try the latest trunk version.
--
D. Richard Hipp
d...@sqlite.org
___
segmentation fault (core dumped)
---
Thanks,
Yongheng & Rui
Richard Hipp 于2019年12月9日周一 下午12:15写道：
> On 12/9/19, Yongheng Chen wrote:
> > Hi,
> >
> > We found a crash bug in sqlite of master branch.
>
> Should
On 12/9/19, Yongheng Chen wrote:
> Hi,
>
> We found a crash bug in sqlite of master branch.
Should now be fixed on trunk.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite
Yongheng Chen, on Monday, December 9, 2019 11:14 AM, wrote...
>
> So should we just report the bugs after another release version? We think the
> sooner
> the bugs get fixed, the better in terms of security, as this approach can
> minimize
> the number of bugs in future release.
Yongheng,
I see. I totally agree with you. A better sqlite is what we all want.
Best.
Yongheng & Rui
> On Dec 9, 2019, at 11:23 AM, Richard Hipp wrote:
>
> On 12/9/19, Yongheng Chen wrote:
>> So should we just report the bugs after another release version?
>
> No. You should report problems as soon
On 12/9/19, Yongheng Chen wrote:
> So should we just report the bugs after another release version?
No. You should report problems as soon as you see them. That is why
we have open-source. That is why all of our changes are out there in
the open where anybody can see them - so that people
So should we just report the bugs after another release version? We think the
sooner the bugs get fixed, the better in terms of security, as this approach
can minimize the number of bugs in future release.
> On Dec 9, 2019, at 10:56 AM, Jose Isaias Cabrera wrote:
>
>
> Since no one
Since no one explains... ;-)
Richard Hipp, on Monday, December 9, 2019 10:53 AM, wrote...
>
> On 12/9/19, Jose Isaias Cabrera, on
> > Error: near "AS": syntax error
> >
> > So, I can't replicate your problem. thanks.
>
> You have to run off of the latest trunk version, as they are fuzzing
> for
On 12/9/19, Jose Isaias Cabrera wrote:
> Error: near "AS": syntax error
>
> So, I can't replicate your problem. thanks.
You have to run off of the latest trunk version, as they are fuzzing
for features that are unreleased.
--
D. Richard Hipp
d...@sqlite.org
Yongheng Chen, on Monday, December 9, 2019 10:16 AM, wrote...
>
> Hi,
>
> We found a crash bug in sqlite of master branch. Here’s the POC
> —
> CREATE TABLE v0 ( v2 DOUBLE CHECK( ( v2 IN ( v2 , v1) ) ) , v1 UNIQUE AS( v2
> > v2 ) ) ;
> INSERT INTO v0 VALUES ( 10 );
Hi,
We found a crash bug in sqlite of master branch. Here’s the POC
—
CREATE TABLE v0 ( v2 DOUBLE CHECK( ( v2 IN ( v2 , v1) ) ) , v1 UNIQUE AS( v2 >
v2 ) ) ;
INSERT INTO v0 VALUES ( 10 );
SELECT v0 . v1 , v0 . v1 FROM v0 JOIN v0 USING ( v1 , v1) ;
—
The bug exists in "SQLite version 3.3
15 matches
Mail list logo
