Summary | Mnemo categories Column |
Queue | Mnemo |
Queue Version | 2.0 |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | |
Requester | g.tranelli (at) inarcassa (dot) it |
Created | 2005-01-04 (5864 days ago) |
Due | |
Updated | 2009-03-18 (4330 days ago) |
Assigned | 2005-01-07 (5861 days ago) |
Resolved | 2005-02-07 (5830 days ago) |
Milestone | |
Patch | No |
Do categories work for you in any other applications? Did you upgrade
from an earlier version of Mnemo? If so, are you sure you ran the
upgrade scripts? Make sure the category field in your database is a
varchar, not an integer.
the help of the hints on this ticket.
The suggestions given worked, but only when I dissected the upgrade
script that was supposed to fix it;
scripts/upgrades/1.1_to_2.0.mysql.sql
I checked out the mnemo_memos table structure, and the memo_category
column was indeed still an integer, which was the cause of the
problem, because the Horde_Categories backend changed that IIRC.
Anyway the upgrade script failed with:
ERROR 1091 (42000) at line 9: Can't DROP 'memo_modified'; check that
column/key exists
Which of course resulted in the portions of the file which correct
memo_category to a VARCHAR(80) were not being run.
Doing a C+P of the remainder of the file directly into a MySQL shell
has fixed the issue.
I'll open up a separate bug about improvements to the upgrade scripts,
because I have some ideas on that, and I think at heart this bug
relates to the use of the upgrade scripts in the wrong order, or
re-use of them.
State ⇒ Not A Bug
State ⇒ Feedback
Do categories work for you in any other applications? Did you upgrade
from an earlier version of Mnemo? If so, are you sure you ran the
upgrade scripts? Make sure the category field in your database is a
varchar, not an integer.
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ Mnemo categories Column
Queue ⇒ Mnemo
"unclassified".