On Tue, Sep 3, 2013 at 9:20 PM, Richard Hipp wrote:
> On Mon, Sep 2, 2013 at 11:07 PM, Alexandre Courbot wrote:
>>
>> Hi everyone, (not subscribed to the ML, please CC)
>>
>> The following happens since 3.8.0 (tested on both 3.8.0 and 3.8.0.1):
>>
>> $ cat |sqlite3
>> create table t1(id INTEGER);
On Tue, Sep 3, 2013 at 9:09 AM, Richard Hipp wrote:
>
>
> We should have a proper fix before too long.
>
>
That fix can now be seen at http://www.sqlite.org/src/info/0303d6bc71
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-use
On Mon, Sep 2, 2013 at 11:07 PM, Alexandre Courbot wrote:
> Hi everyone, (not subscribed to the ML, please CC)
>
> The following happens since 3.8.0 (tested on both 3.8.0 and 3.8.0.1):
>
> Could this be related to the new query planner?
>
No. This seems to be due to the new optimization that st
On Mon, Sep 2, 2013 at 11:07 PM, Alexandre Courbot wrote:
> Hi everyone, (not subscribed to the ML, please CC)
>
> The following happens since 3.8.0 (tested on both 3.8.0 and 3.8.0.1):
>
> $ cat |sqlite3
> create table t1(id INTEGER);
> create table t2(id INTEGER, v INTEGER);
> insert into t1 val
Hi everyone, (not subscribed to the ML, please CC)
The following happens since 3.8.0 (tested on both 3.8.0 and 3.8.0.1):
$ cat |sqlite3
create table t1(id INTEGER);
create table t2(id INTEGER, v INTEGER);
insert into t1 values(1);
select distinct t1.id from t1 left join t2 on t2.id = t1.id order
5 matches
Mail list logo