Re: [sqlite] Behavior change in group by in 3.8.2 when compared with 3.7.7

On Thu, Jan 9, 2014 at 7:41 AM, Navaneeth K N wrote: > I am seeing a change in the results returned for a query in SQLIte 3.8.2 > version. The query used to return expected results with 3.7.7 and when I > updated to 3.8.2, it changed the results. > > Here is a test case: > >

Re: [sqlite] Behavior change in group by in 3.8.2 when compared with 3.7.7

On 01/09/2014 03:38 PM, Dominique Devienne wrote: On Thu, Jan 9, 2014 at 7:41 AM, Navaneeth K N wrote: I am seeing a change in the results returned for a query in SQLIte 3.8.2 version. The query used to return expected results with 3.7.7 and when I updated to 3.8.2, it

Re: [sqlite] Behavior change in group by in 3.8.2 when compared with 3.7.7

On Thu, Jan 9, 2014 at 10:02 AM, Dan Kennedy wrote: > On 01/09/2014 03:38 PM, Dominique Devienne wrote: > >> Someone will soon point out exactly what commit/bug was fixed in SQLite >> I'm sure. >> > > Probably this: > http://www.sqlite.org/src/info/f2d175f975 > > Fix

Re: [sqlite] Behavior change in group by in 3.8.2 when compared with 3.7.7

On Thu, Jan 9, 2014 at 10:18 AM, Dominique Devienne wrote: > On Thu, Jan 9, 2014 at 10:02 AM, Dan Kennedy wrote: > >> On 01/09/2014 03:38 PM, Dominique Devienne wrote: >> >>> Someone will soon point out exactly what commit/bug was fixed in SQLite >>>

[sqlite] Compiler warning: Unused variable ‘pFd'

Hello, I am using SQLite 3.8.2 for my iOS projects in Xcode 5.0.2. After updating to version 3.8.2 I am getting the following compiler warning: sqlite3.c:28141:13: Unused variable ‘pFd’ When looking into the code I see starting at line 28141: static int unixUnfetch(sqlite3_file *fd, i64 iOff,

Re: [sqlite] Compiler warning: Unused variable 'pFd'

This is my list of disabled compiler warnings (using GCC in "absolutely most pedantic" mode) required to compile sqlite (and even omitting FTS and some other stuff). -Wno-aggregate-return -Wno-bad-function-cast -Wno-cast-qual -Wno-empty-body -Wno-format-extra-args -Wno-format-nonliteral

[sqlite] integrity check

Hi all, Executed integrity check for database before application starts. Sometimes, it takes 1 minute. Other times, it finishes within 2 seconds. How integrity check works? can somebody explain why it takes less time. Thanks, dd ___ sqlite-users

Re: [sqlite] integrity check

On Thu, Jan 9, 2014 at 8:29 AM, dd wrote: > Hi all, > > Executed integrity check for database before application starts. > Sometimes, it takes 1 minute. Other times, it finishes within 2 > seconds. How integrity check works? can somebody explain why it takes > less time.

Re: [sqlite] integrity check

Applied encryption on top of sqlite. Now, I suspect on encryption. Thanks for prompt response. On Thu, Jan 9, 2014 at 5:38 PM, Richard Hipp wrote: > On Thu, Jan 9, 2014 at 8:29 AM, dd wrote: > >> Hi all, >> >> Executed integrity check for database before

[sqlite] Saw something interesting in the debugger...

I've got a multi-threaded iOS app. Each thread has its own long-lived DB connection. I was debugging a "stuttering" in the UI thread and broke into the debugger during one of the pauses. I found the UI thread and a worker thread, both in the DB, both in the default busy handler, both taking a

Re: [sqlite] Saw something interesting in the debugger...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/01/14 08:53, Ward Willats wrote: > I found the UI thread and a worker thread, both in the DB, both in the > default busy handler, both taking a 1 second sleep. > > I expected to see a third thread in the DB doing some work while the > other two

Re: [sqlite] Saw something interesting in the debugger...

On Jan 9, 2014, at 10:10 AM, Roger Binns wrote: > The default busy handler (see sqliteDefaultBusyCallback in source) sleeps > for these amount of milliseconds: > > { 1, 2, 5, 10, 15, 20, 25, 25, 25, 50, 50, 100 }; > > However on non-Windows if you do not have

Re: [sqlite] Saw something interesting in the debugger...

Op 9 jan 2014, om 19:50 heeft Ward Willats het volgende geschreven: BUT, I was wondering if there are scenarios where only two threads can bounce each other into busy sleep like two bocci balls colliding? (one thread wanted a read lock, the other a BEGIN EXCLUSIVE write lock) On Jan 9,

Re: [sqlite] fstat warning with SQLite 3.8.1 on Android

Some analysis shows that the call to fstat fails because the filename being passed into it is null. This seems to be specific to Android as I tried the same code on iOS and it did not produce the same warning message. I feel it is somehow related to the temp file storage on Android, but that is

[sqlite] Visual Studio 2013 RC vs. RTM issue

I don't usually like shooting off an email to the list before having analyzed the entire problem sufficiently, but given that a whole day was spent on this already I wanted to see if any of this sounds familiar to anyone reading this: In my project I am using SQLite 3.7.16.1 which on Windows gets