Hi everyone,
I hit some failures in fts3conf.test while buidling latest version of
sqlite for the ppc64 architecture:
! fts3conf-3.1 expected: [X'0100000002000000']
! fts3conf-3.1 got: [X'0000000100000002']
! fts3conf-3.2 expected: [X'0200000003000000']
! fts3conf-3.2 got: [X'0000000200000003']
! fts3conf-3.3 expected: [X'0200000005000000']
! fts3conf-3.3 got: [X'0000000200000005']
! fts3conf-3.4 expected: [X'0100000006000000']
! fts3conf-3.4 got: [X'0000000100000006']
! fts3conf-3.5 expected: [X'0100000006000000']
! fts3conf-3.5 got: [X'0000000100000006']
! fts3conf-3.6 expected: [X'0100000002000000']
! fts3conf-3.6 got: [X'0000000100000002']
! fts3conf-3.8 expected: [X'0200000002000000']
! fts3conf-3.8 got: [X'0000000200000002']
From what I understand the issue seems to be caused by how the blob is
stored in memory on a big-endian architecture and since the query
function just dumps the value into a string, it differs from what is
expected.
This seems like an issue that needs to be fixed in the test suite rather
than in the code, but would like to make sure before writing any
patches. Does sqlite's test suite even support arch-specific results?
Thanks for any help with this.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
