-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Kettler wrote:
A quick diff of the 3.2 and 3.3 versions of these files shows this table
was changed:
CREATE TABLE bayes_token (
id int(11) NOT NULL default '0',
token char(5) NOT NULL default '',
spam_count int(11) NOT NULL
On Sat, Feb 13, 2010 at 10:33:08AM -0600, David Morton wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Kettler wrote:
A quick diff of the 3.2 and 3.3 versions of these files shows this table
was changed:
CREATE TABLE bayes_token (
id int(11) NOT NULL default '0',
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik K wrote:
So token was both a primary key, and an index, which is redundant.
How is that redundant? If you search for only a token, it would not be
indexed, and would perform very poorly.
As you didn't bother to check SpamAssassin
On 2/13/2010 11:33 AM, David Morton wrote:
So token was both a primary key, and an index, which is redundant.
How is that redundant? If you search for only a token, it would not be
indexed, and would perform very poorly.
Because it is the primary key, which is by definition, an index!!!
On Sat, 13 Feb 2010, Matt Kettler wrote:
On 2/13/2010 11:33 AM, David Morton wrote:
So token was both a primary key, and an index, which is redundant.
How is that redundant? If you search for only a token, it would not be
indexed, and would perform very poorly.
Because it is the primary
I looked at our bayes schema and at the schema in
../docs/sql/bayes_mysql.sql and I can't find the redundant index
mentioned in the SA 3.30 upgrade/changes documents.
did I miss something? or did I remove it years ago anyway?
--
Michael Scheidell, CTO
Phone: 561-999-5000, x 1259
*| *SECNAP
On 2/12/2010 2:51 PM, Michael Scheidell wrote:
I looked at our bayes schema and at the schema in
../docs/sql/bayes_mysql.sql and I can't find the redundant index
mentioned in the SA 3.30 upgrade/changes documents.
did I miss something? or did I remove it years ago anyway?
A quick diff of
