I've outputted the results of _sqlite3_libversion and they have verified that the OBJ files are self contained. However, doing so has resulted in one new piece of data. The two versions are:
3.6.17 3.7.9 I don't know if that information makes any difference, but you should have all potentially relevant information. I did add an assertion which runs during initialization to ensure that the version is as expected. I have confirmed that both the shell application and the full application concur on version numbers. On Tue, Jan 10, 2012 at 10:35 AM, John Elrick <john.elr...@fenestra.com> wrote: > On Tue, Jan 10, 2012 at 10:14 AM, Richard Hipp <d...@sqlite.org> wrote: >> On Tue, Jan 10, 2012 at 10:08 AM, John Elrick >> <john.elr...@fenestra.com>wrote: >> >>> On Tue, Jan 10, 2012 at 8:31 AM, Richard Hipp <d...@sqlite.org> wrote: >>> > On Tue, Jan 10, 2012 at 8:14 AM, John Elrick <john.elr...@fenestra.com >>> >wrote: >>> > >>> >> I will have to get back to you on this. While running tests against >>> >> isolated queries, I noticed an unusual circumstance. When I isolate >>> >> the queries into a test program, running through our present >>> >> libraries, 3.7.9 is roughly 4 times faster executing the exact same >>> >> queries where it is running roughly 5 times slower in the context of >>> >> the application. As those queries do not execute in the same order, I >>> >> suspect that page swapping and caching issues may be involved. I'm >>> >> proceeding on that assumption. >>> >> >>> > >>> > >>> > Are you using the same compile-time options when building your >>> application >>> > as were used when building the shell program? >>> >>> Yes. >>> >> >> Have you run "SELECT sqlite_source_id();" to verify that your build is >> really picking up the version of SQLite that you think it is? >> >> Do you have code like this in your application: >> >> assert( sqlite3_libversion_number()==SQLITE_VERSION_NUMBER ); >> assert( strcmp(sqlite3_sourceid(),SQLITE_SOURCE_ID)==0 ); >> assert( strcmp(sqlite3_libversion(),SQLITE_VERSION)==0 ); >> >> To verify that your SQLite source code and "sqlite3.h" header file match? > > Nope. I assume that the resulting .OBJ files are self contained. > I'll run the tests you suggest just to make certain. -- John Elrick Fenestra Technologies 540-868-1377 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users