Re: [sqlite] affinity critical problem with 3.8.5 - IN single value optimisation

[Richard Hipp]

On Tue, Jul 8, 2014 at 10:35 AM, Hinrichsen, John 
wrote:

> This is a nasty bug; I do not see any follow-up regarding a fix.
>

Fix is here (I think): http://www.sqlite.org/src/info/92f7ad43dbfe


>
>
> On Thu, Jun 26, 2014 at 9:17 AM, Guillaume Fougnies <
> guilla...@eulerian.com>
> wrote:
>
> > Hi,
> >
> > It seems there's a problem with 3.8.5 and its affinity behavior.
> > It's quite critical.
> >
> > --- CUT ---
> > sqlite> CREATE TABLE T (v text);
> > sqlite> insert into T values('1');
> > sqlite> insert into T values('2');
> > sqlite> select v from T where v=1;
> > 1
> > sqlite> select v from T where v='1';
> > 1
> > sqlite> select v from T where v IN(1);
> > sqlite> select v from T where v IN('1');
> > 1
> > sqlite> select v from T where v IN(1,2);
> > 1
> > 2
> > sqlite> select v from T where v IN('1','2');
> > 1
> > 2
> > --- /CUT ---
> >
> >
> > It must be linked to this change:
> >
> > "Render expressions of the form "x IN (?)" (with a single value in the
> > list on the right-hand side of the IN operator) as if they where "x==?",
> > Similarly optimize "x NOT IN (?)""
> >
> > Best regards,
> > --
> > Guillaume FOUGNIES
> > Eulerian Technologies
> > ___
> > sqlite-users mailing list
> > sqlite-users@sqlite.org
> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> >
>
> --
>
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee, you should not
> disseminate, distribute, alter or copy this e-mail. Please notify the
> sender immediately by e-mail if you have received this e-mail by mistake
> and delete this e-mail from your system. E-mail transmissions cannot be
> guaranteed to be secure or without error as information could be
> intercepted, corrupted, lost, destroyed, or arrive late or incomplete. The
> sender, therefore, does not accept liability for any errors or omissions in
> the contents of this message which arise during or as a result of e-mail
> transmission. If verification is required, please request a hard-copy
> version. This message is provided for information purposes and should not
> be construed as a solicitation or offer to buy or sell any securities or
> related financial instruments in any jurisdiction.
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] affinity critical problem with 3.8.5 - IN single value optimisation

[Jan Nijtmans]

2014-07-08 16:35 GMT+02:00 Hinrichsen, John :
> This is a nasty bug; I do not see any follow-up regarding a fix.




Regards,
 Jan Nijtmans
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] affinity critical problem with 3.8.5 - IN single value optimisation

[Hinrichsen, John]

This is a nasty bug; I do not see any follow-up regarding a fix.


On Thu, Jun 26, 2014 at 9:17 AM, Guillaume Fougnies 
wrote:

> Hi,
>
> It seems there's a problem with 3.8.5 and its affinity behavior.
> It's quite critical.
>
> --- CUT ---
> sqlite> CREATE TABLE T (v text);
> sqlite> insert into T values('1');
> sqlite> insert into T values('2');
> sqlite> select v from T where v=1;
> 1
> sqlite> select v from T where v='1';
> 1
> sqlite> select v from T where v IN(1);
> sqlite> select v from T where v IN('1');
> 1
> sqlite> select v from T where v IN(1,2);
> 1
> 2
> sqlite> select v from T where v IN('1','2');
> 1
> 2
> --- /CUT ---
>
>
> It must be linked to this change:
>
> "Render expressions of the form "x IN (?)" (with a single value in the
> list on the right-hand side of the IN operator) as if they where "x==?",
> Similarly optimize "x NOT IN (?)""
>
> Best regards,
> --
> Guillaume FOUGNIES
> Eulerian Technologies
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>

-- 

This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee, you should not 
disseminate, distribute, alter or copy this e-mail. Please notify the 
sender immediately by e-mail if you have received this e-mail by mistake 
and delete this e-mail from your system. E-mail transmissions cannot be 
guaranteed to be secure or without error as information could be 
intercepted, corrupted, lost, destroyed, or arrive late or incomplete. The 
sender, therefore, does not accept liability for any errors or omissions in 
the contents of this message which arise during or as a result of e-mail 
transmission. If verification is required, please request a hard-copy 
version. This message is provided for information purposes and should not 
be construed as a solicitation or offer to buy or sell any securities or 
related financial instruments in any jurisdiction.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] affinity critical problem with 3.8.5 - IN single value optimisation

[Guillaume Fougnies]

Hi,

It seems there's a problem with 3.8.5 and its affinity behavior.
It's quite critical.

--- CUT ---
sqlite> CREATE TABLE T (v text);
sqlite> insert into T values('1');
sqlite> insert into T values('2');
sqlite> select v from T where v=1;
1
sqlite> select v from T where v='1';
1
sqlite> select v from T where v IN(1);
sqlite> select v from T where v IN('1');
1
sqlite> select v from T where v IN(1,2);
1
2
sqlite> select v from T where v IN('1','2');
1
2
--- /CUT ---


It must be linked to this change:

"Render expressions of the form "x IN (?)" (with a single value in the list on 
the right-hand side of the IN operator) as if they where "x==?", Similarly 
optimize "x NOT IN (?)""

Best regards,
--
Guillaume FOUGNIES
Eulerian Technologies
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users