Re: [sqlite] [BUG] Adding an index changes query result

On Wed, Jun 9, 2010 at 3:34 PM, Israel Lins Albuquerque < israel...@polibrasnet.com.br> wrote: > > > I make the possible soluction I did't know if this is the best but is this: > The correct fix is checked in here: http://www.sqlite.org/src/vinfo/6eb058dda8 -- - D. Richard

Re: [sqlite] [BUG] Adding an index changes query result

qlite-users@sqlite.org> Enviadas: Quarta-feira, 9 de Junho de 2010 16:34:22 Assunto: Re: [sqlite] [BUG] Adding an index changes query result I make the possible soluction I did't know if this is the best but is this: /

Re: [sqlite] [BUG] Adding an index changes query result

I make the possible soluction I did't know if this is the best but is this: // Index: D:/FS_trunk/devpalm_01/poli_sqlite_lib/src/expr.c ===

Re: [sqlite] [BUG] Adding an index changes query result

On Wed, Jun 9, 2010 at 11:29 AM, Pavel Ivanov wrote: > > Perhaps this is the way it was supposed to work. But presence of index > > does affect something, so I assumed it somehow messes affinity (what > else?). > > Comparison of numbers and strings without affinities is

Re: [sqlite] [BUG] Adding an index changes query result

> Perhaps this is the way it was supposed to work.  But presence of index > does affect something, so I assumed it somehow messes affinity (what else?). Comparison of numbers and strings without affinities is supposed to work this way, yes. In this case though I think you're right - comparison on

Re: [sqlite] [BUG] Adding an index changes query result

2010/6/9 Pavel Ivanov > You can see that these 2 cases compare the same way. They both show > that string is always greater than number and thus '11' > 2 and '2' > > 11. And no affinity rules are applicable here because you use > constants which don't have any affinity.

Re: [sqlite] [BUG] Adding an index changes query result

bug to me. Michael D. Black Senior Scientist Northrop Grumman Mission Systems From: sqlite-users-boun...@sqlite.org on behalf of Pavel Ivanov Sent: Wed 6/9/2010 9:35 AM To: General Discussion of SQLite Database Subject: Re: [sqlite] [BUG] Adding an index changes q

Re: [sqlite] [BUG] Adding an index changes query result

Eduardo, You should never check correctness of what SQLite is doing in postgresql or mysql. They are different database engines with different principles. SQLite does exactly the right thing in this case and exactly how it's documented. (I don't mean dependence of query result on index existence

Re: [sqlite] [BUG] Adding an index changes query result

2010-06-09 Tomash Brechko : > With SQLite 3.6.23.1 I see the following: > >  $ ./sqlite3 /tmp/a.sqlite >  SQLite version 3.6.23.1 >  Enter ".help" for instructions >  Enter SQL statements terminated with a ";" >  sqlite> CREATE TABLE t (c1 INTEGER, c2 INTEGER); >  sqlite>

Re: [sqlite] [BUG] Adding an index changes query result

This is a bit weird...it appears it's just the = operator causing this... sqlite> select * from t where c1>=5 and c2>0 and c2<='2'; sqlite> select * from t where c1<=5 and c2>0 and c2<='2'; sqlite> select * from t where c1=5 and c2>0 and c2<='2'; 5|5 sqlite> drop index t_c1_c2; sqlite> select *