https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7941
Bug ID: 7941
Summary: sql/txrep_sqlite.sql: typo in UPDATE trigger column
name breaks txrep DB
Product: Spamassassin
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: spamassassin
Assignee: dev@spamassassin.apache.org
Reporter: mail@maciej.szmigiero.name
Target Milestone: Undefined
sql/txrep_sqlite.sql has a typo in UPDATE trigger column name: [1] should be
[2] (note the "hot" vs "hit").
This typo breaks UPDATE operations on txrep DBs created from that script.
While at it I would suggest applying the attached patch to
"SQLBasedAddrList.pm" so errors like this one (happening at DBI prepare
operation) are correctly handled and logged, instead of printing just [3] which
doesn't give a clue what is wrong.
References:
[1]: WHEN NEW.last_hot < OLD.last_hit
[2]: WHEN NEW.last_hit < OLD.last_hit
[3]: Can't call method "execute" on an undefined value
--
You are receiving this mail because:
You are the assignee for the bug.
Bug ID: 7941
Summary: sql/txrep_sqlite.sql: typo in UPDATE trigger column
name breaks txrep DB
Product: Spamassassin
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: spamassassin
Assignee: dev@spamassassin.apache.org
Reporter: mail@maciej.szmigiero.name
Target Milestone: Undefined
sql/txrep_sqlite.sql has a typo in UPDATE trigger column name: [1] should be
[2] (note the "hot" vs "hit").
This typo breaks UPDATE operations on txrep DBs created from that script.
While at it I would suggest applying the attached patch to
"SQLBasedAddrList.pm" so errors like this one (happening at DBI prepare
operation) are correctly handled and logged, instead of printing just [3] which
doesn't give a clue what is wrong.
References:
[1]: WHEN NEW.last_hot < OLD.last_hit
[2]: WHEN NEW.last_hit < OLD.last_hit
[3]: Can't call method "execute" on an undefined value
--
You are receiving this mail because:
You are the assignee for the bug.