SQLite stores the verison number of the librrary in the database header. Different SQlite libraries on different computers would cause this error.
Paul www.sandersonforensics.com skype: r3scue193 twitter: @sandersonforens Tel +44 (0)1326 572786 http://sandersonforensics.com/forum/content.php?195-SQLite-Forensic-Toolkit -Forensic Toolkit for SQLite email from a work address for a fully functional demo licence On 19 December 2017 at 12:32, Karl Forner <karl.for...@gmail.com> wrote: > Hello, > > I encountered a weird behavior recently. > The exact same code (executed from a docker container using the same image) > produced a different database file on two computers, as verified by a MD5 > or sha256 hash of the two files. > But using the* .sha3sum* of sqlite3.exe I could check that the contents of > the two databases are indeed identical. > > To sum up, same content, but the files are somewhat different. > > Is this something expected or known ? > If so, is there a way to prevent this ? > > Our use case if that we track the sha256 hashes of the files, that could > have been produced on different computers to know of the outputs are up to > date. Until now, since ~ 4 years it has always seem to work. > > Thanks. > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
