2015-10-15 18:18 GMT+02:00 Bruce Blackwell <digimetrix at gmail.com>:
> I do not know if it is significant or not, but this is the first time I
> have ever seen this happen.
>
> sqlite3.dll from sqlite-dll-win32-x86-3090000.zip reports
> sqlite_source_id() as 2015-10-14 18:30:13
> a43bb2b5cf9c7c19edbce37c883826eb0f7ed764
> However, the amalgamation files have #define SQLITE_SOURCE_ID "2015-10-14
> 12:29:53 a721fc0d89495518fe5612e2e3bbc60befd2e90d"
The SOURCE_ID can be found in the SQLite fossil repository, in order
to see exactly which sources the dll was compiled from. e.g. version 3.9.0
is here:
<http://www.sqlite.org/src/info/a721fc0d89495518fe5612e2e3bbc60befd2e90d>
The source-id from the compiled sqlite3.dll should be available in the same way:
<http://www.sqlite.org/src/info/a43bb2b5cf9c7c19edbce37c883826eb0f7ed764>
but .... it isn't. Most likely, the dll was compiled by cherry-picking
[01d3ee7bbe4feeb8] (containing a dll symbol fix) to the 3.9.0 version.
Most likely, this merge was committed to a local fossil repository (which
created the alternative source_id), but never pushed back to the official
repository. That's the best answer I can give.
Regards,
Jan Nijtmans
