I got the timestanp field added to the bayee_seen table. I don't know why but
ALTER TABLE bayes_seen
ADD lastupdate timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE
CURRENT_TIMESTAMP;
did not work as it set all of the lastupdate fields to '0000-00-00 00:00:00'
which apparently is *not* NULL. Thanks to Jari for this:
UPDATE bayes_seen
SET lastupdate = CURRENT_TIMESTAMP
WHERE lastupdate = '0000-00-00 00:00:00' ;
which fixed me up. Maybe it would have worked with InnoDB and not with NyISAM.
All my tables are MyISAM.
I have two questions:
I. I am running MySQL version 5.067 which apparently is not enough to be
allowed to run InnoDB. The questions is this: I thought that InnoDB was going
to consume *more* resources because the purpose of it was to support
transactions. Am I wrong? If I convert to a higher rev of MySQL and get InnoDB
will I get *better* performance?
II. The other question I asked earlier and didn't get an answer to, is...
Is there a consensus on the optimal time that the bayes_seen and awl tables
should be expired? Is 3 months good? Will 6 months not buy me anything but
hurt performance? Will two months make my bayes tables less accurate?
--
Time flies like the wind. Fruit flies like a banana. Stranger things have .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net
signature.asc
Description: OpenPGP digital signature
