On Tue, Mar 5, 2013 at 2:29 PM, Richard Hipp <d...@sqlite.org> wrote:
> > > On Sun, Mar 3, 2013 at 2:48 PM, Tom Matrix <ratomat...@gmail.com> wrote: > >> >> I’ve encountered a problem, which is hardly reproducable on arbitrary >> databases, therefore I attached one. >> > > A simple, reproducible test case for (what we think is) your problem can > be seen in this ticket: > > www.sqlite.org/src/tktview/fc7bd6358f59b > > This bug has been latent in SQLite for almost four years and you are the > first to hit it. Probably this is because not many applications contain > A=B in the WHERE clause where A is a text expression and B is an integer > expression. You can probably work around the problem by changing your > schema so that entries.measurementid is an integer rather than text. This > does not excuse SQLite: It is still getting the wrong answer and needs to > be fixed. We are working on a fix now. But a simple change to your schema > will work around the problem and get you going even before that fix is > available. > This problem has now been fixed on trunk (see http://www.sqlite.org/src/info/7097241c12 for details). There is also an amalgamation including the fix at the http://www.sqlite.org/draft/download.html draft download page. The release of version 3.7.16 will likely be delayed for a few days to give folks a better changes to test this fix. The version 3.7.16 status board at http://www.sqlite.org/checklists/3071600 which was formerly showing a lot of green has been reset as we intend to rerun all tests. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
