On Thu, Mar 8, 2012 at 6:27 PM, Alan Chandler <a...@chandlerfamily.org.uk>wrote:

> On 08/03/12 22:44, Alan Chandler wrote:
>
>> I have been running a financial management application application I
>> wrote for a number of years.  My "production" version runs on Debian stable
>> system as a result is running sqlite v3.7.3.  My personal development
>> machine is running Debian unstable and as a result has sqlite 3.7.10.
>>
>> Earlier this week I discovered a bug in a rarely used part of the
>> application, so took a copy of the production database and ran it on my
>> development machine. I quickly found that and fixed it, but another major
>> element of the application appeared to give some strange results.
>>
>> I have spend some down tracking down what caused the problem, and it
>> seems to be a difference in how sqlite 3.7.3 and sqlite 3.7.10 processes
>> the sql.  It seems to me that the later release gets things wrong - but it
>> might be that the newer version has some sort of PRAGMA that I am not using
>> right.  So I would like to ask here where I am going wrong.
>>
>>
> Things have now got stranger.  I just saw the post on the e-mail list for
> sqlitestudio and thought that looks interesting, so I have now downloaded
> it.  It seems to be using sqlite 3.7.8
>
> It works correctly, and the very same sql using sqlite manager in Mozilla
> goes wrong (this is linked to sqlite 3.7.10)


The suspect change at http://www.sqlite.org/src/info/b23ae13187 first
appeared in version 3.7.10.


>
>
> --
> Alan Chandler
> http://www.chandlerfamily.org.**uk <http://www.chandlerfamily.org.uk>
>
> ______________________________**_________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users<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

Reply via email to