On 8/4/17, jose isaias cabrera <jic...@barrioinvi.net> wrote:
>
> Right now, when I went to a machine that I had upgraded with a
> snapshot, I saw that the version was 3.20.0.  But when I compared the DLL
> file size and date, they were different.  It would be nice for pre-releases
> to have something to distinguish them with the new one.

That "something" is the "source-id".  You can access the source-id
from C-code using

    SQLITE_SOURCE_ID   (https://sqlite.org/c3ref/c_source_id.html)

or

    sqlite3_sourceid()  (https://sqlite.org/c3ref/libversion.html)

Or you can access the information from SQL using

    sqlite_source_id()  (https://sqlite.org/lang_corefunc.html#sqlite_source_id)

The 3.20.0 release version has a source-id of

    "2017-08-01 13:24:15
9501e22dfeebdcefa783575e47c60b514d7c2e0cad73b2a496c0bc4b680900a8"

The snapshots have an earlier date.  You can trace the version of
SQLite you are running back to a particular source-code repository
check-in using the hash.  Let $HASH be some prefix of the hash shown
at the end of the source-id.  (8 characters is usually plenty.)  Then
you can find the check-in, in context, by visiting
"sqlite3.org/src/timeline?c=$HASM".  For example:

    https://sqlite.org/src/timeline?c=9501e22d

-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to