tackling sqlite byte-order problem

[Matthias Andree]

David Relson <relson at osagesoftware.com> writes:

>> Yup. I'd think we'd better add .ENDIAN32 at creation time to remove
>> hunting for dates. The YYYY must be >= 2002 (first bogofilter release)
>> and the MMDD <= 1231. We can gather dates almost everywhere, token
>> timestamp, .WORDLIST_VERSION, we can sanity check .ROBX, but whenever
>> the database is open for update, we'd better place an .ENDIAN32 tag for
>> efficiency.
>
> It seems that this is needed only for sqlite3, because the other
> databases support is_swapped(), right?

I'm not sure about TDB and QDBM. QDBM appears not to support sharing
database files across endianness, TDB is virtually undocumented and
documentation and code are notoriously out of synch.

I don't want to make a sqlite3-local solution if the code can be reused
for another DB backend.

-- 
Matthias Andree