To answer Ben's question, "Out of curiosity, how did this SQL error come to
your attention in the
first place?"
I was troubleshooting another issue and set $log_level = 5 and noticed the
errors.
> On 4/25/2013 11:55 AM, Matus UHLAR - fantomas wrote:
>
> ...
>
> My understanding is that it's better (with respect to performance and
> atomicity) to attempt the INSERT and have it fail than to check if the
> ID/token combination already exists and UPDATE it if it does.
Please note that it wou
On 4/25/2013 11:55 AM, Matus UHLAR - fantomas wrote:
>> On Thu, Apr 25, 2013 at 1:47 PM, Matus UHLAR - fantomas
>> wrote:
>>> I don't think so... IIRC the "REPLACE INTO" deletes existing record and
>>> inserts new one, does not update existing. This caused some issues
>>> for me
>>> some ~10 year
On Thu, Apr 25, 2013 at 1:47 PM, Matus UHLAR - fantomas
wrote:
I don't think so... IIRC the "REPLACE INTO" deletes existing record and
inserts new one, does not update existing. This caused some issues for me
some ~10 years ago, so i switched to the update or insert.
On 25.04.13 16:36, Matthias
On Thu, Apr 25, 2013 at 1:47 PM, Matus UHLAR - fantomas
wrote:
> I don't think so... IIRC the "REPLACE INTO" deletes existing record and
> inserts new one, does not update existing. This caused some issues for me
> some ~10 years ago, so i switched to the update or insert.
>
"REPLACE INTO" is a
On 24.04.13 17:01, psychobyte wrote:
in the bayes case, the table is bayes_token and indeed
Mail::SpamAssassin::BayesStore::SQL is INSERTING into the table via
_put_tokens().
my $insertsql = "INSERT INTO bayes_token
(id, token, spam_count, ham_count, atime)
Well,
in the bayes case, the table is bayes_token and indeed
Mail::SpamAssassin::BayesStore::SQL is INSERTING into the table via
_put_tokens().
my $insertsql = "INSERT INTO bayes_token
(id, token, spam_count, ham_count, atime)
VALUES (?,?,?,?,?)";
so,
On 4/24/2013 2:42 PM, psychobyte wrote:
> Hi,
>
> I've noticed that SA is getting a lot of "Duplicate entry" errors for
> AWL and bayes plugins. I can verify that the sql schema is up to date
> for SA 3.3.1-r4 and I've tried retraining the bayes db. Any hints on how
> to troubleshoot this?
>
>
