spamassassin-dev September 2011 archive
Main Archive Page > Month Archives  > spamassassin-dev archives
spamassassin-dev: [Bug 6663] Use unsigned database fields for in

[Bug 6663] Use unsigned database fields for int

From: <bugzilla-daemon_at_nospam>
Date: Thu Sep 22 2011 - 08:26:57 GMT
To: dev@spamassassin.apache.org

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6663

--- Comment #6 from Michiel Hazelhof <michiel@hazelhof.nl> 2011-09-22 08:26:57 UTC ---
Sorry I forgot to add the sql file.
Setting fields like bayes_token.id to unsigned , allows them to contain higher
numbers and potentially avoid some problems.

All fields which never contain negative integers should be unsigned (unsigned:
0 to 4,294,967,295 and signed: -2,147,438,648 to 2,147,438,647).

I am not sure about the following fields regarding to unsigned:
bayes_expire.runtime
bayes_vars.last_atime_delta
bayes_vars.last_expire_reduce

As for UTF8 it reduces memory usage a bit (I guess, just my measurements) and
is capable of holding nearly all possible characters (that should be used
anyway). Also defining a default set should help with debugging purposes as
well since everybody should be having the same set.

-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.