tackling sqlite byte-order problem

[David Relson]

On Thu, 10 Feb 2005 02:02:34 +0100
Matthias Andree wrote:

> David Relson <relson at osagesoftware.com> writes:
> 
> > My bad.  It's binary, not BCD.  Splitting would be "divide by 10000" and
> > check for reasonable results.
> 
> 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?