Re: [sqlite] Query on bug fix for ticket 7ffd1ca1d2ad4ec

2017-07-13 Thread mohan_gn
Hi Simon,

Thank you for your suggestion. Will check it out.

Regards,
Mohan



--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Query-on-bug-fix-for-ticket-7ffd1ca1d2ad4ec-tp96175p96608.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] Query on bug fix for ticket 7ffd1ca1d2ad4ec

2017-07-10 Thread Simon Slavin


On 10 Jul 2017, at 9:17am, mohan_gn  wrote:

> Since our product is already in field with older
> version of SQLite, we want to know this bug's impact. We use simple queries
> like 'select * from abc where col1=123 and col2=456'. We don't use any
> JOINs, VIEWs, nested queries. The tables we use do have primary keys and
> foreign keys. 
> So I wanted to know whether in our cases the bug will impact and whether we
> may be affected.

You do not say which version of SQLite your product uses.  If it’s earlier than 
3.7.7 or later than 3.16.2 then it is not affected.

Temporary indexes are made when there is no index ideally suited to your ORDER 
BY and WHERE clauses.  If your queries execute quickly because you have made 
the right indexes then this bug will not affect you.  See section 12.0 of



You can execute each of your SELECT/INSERT/UPDATE/DELETE commands with EXPLAIN 
QUERY PLAN in front of it, and check the output to see if it mentions a 
temporary index:



Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] Query on bug fix for ticket 7ffd1ca1d2ad4ec

2017-07-10 Thread mohan_gn
Thank you for the reply. 
I know it has been fixed. Since our product is already in field with older
version of SQLite, we want to know this bug's impact. We use simple queries
like 'select * from abc where col1=123 and col2=456'. We don't use any
JOINs, VIEWs, nested queries. The tables we use do have primary keys and
foreign keys. 
So I wanted to know whether in our cases the bug will impact and whether we
may be affected. 

Thank you,
Mohan




--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Query-on-bug-fix-for-ticket-7ffd1ca1d2ad4ec-tp96175p96577.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] Query on bug fix for ticket 7ffd1ca1d2ad4ec

2017-07-10 Thread Simon Slavin


On 10 Jul 2017, at 7:15am, mohan_gn  wrote:

> Could anyone please answer above query? 

Do you mean this bug ?



If so, the bug was fixed in January.  Please download the latest version of 
SQLite and see whether you can reproduce the bug.

Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


Re: [sqlite] Query on bug fix for ticket 7ffd1ca1d2ad4ec

2017-07-10 Thread mohan_gn
Hi All,

Could anyone please answer above query? 

Thank you very much,
Mohan



--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Query-on-bug-fix-for-ticket-7ffd1ca1d2ad4ec-tp96175p96575.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


[sqlite] Query on bug fix for ticket 7ffd1ca1d2ad4ec

2017-06-13 Thread Mohandas G Nayak
Hi All,

We are using SQLite 3.7.16.1 in our product which has been released to market 
sometime back. 
We have been analysing releases of SQLite from 3.7.16 to 3.19.2 to see if we 
need to upgrade the SQLite 
for the software that is already deployed in the field. For this purpose we use 
release history of 
SQLite, go through the bug fixes done and check if we need to upgrade SQLite 
depending on the bug fix 
done.
While doing this analysis we came across this fix: "Use the correct affinity 
for columns of automatic 
indexes. Ticket 
7ffd1ca1d2ad4ec(https://www.sqlite.org/src/info/7ffd1ca1d2ad4ec)." which was 
fixed in 
3.17.0 The description of the bug fix is not detailed and hence we don't know 
if we need to upgrade 
SQLite version.
We use simple queries like 'select * from abc where col1=123 and col2=456'. We 
dont use any JOINs, 
VIEWs, nested queries. The tables we use do have primary keys and foreign keys. 
Please let us know in 
which cases the bug will impact and whether we may be affected.

Thank you,
Mohan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users