[Tickets #10003] Re: unknown address book "localsql"
bugs at horde.org
bugs at horde.org
Tue Aug 2 06:34:53 UTC 2011
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/10003
------------------------------------------------------------------------------
Ticket | 10003
Updated By | Michael Rubinsky <mrubinsk at horde.org>
Summary | unknown address book "localsql"
Queue | Turba
Version | Git master
Type | Bug
State | Not A Bug
Priority | 1. Low
Milestone |
Patch |
Owners | Michael Rubinsky
------------------------------------------------------------------------------
Michael Rubinsky <mrubinsk at horde.org> (2011-08-02 06:34) wrote:
> When looking into database I see that this user somehow got new line
> into his preference:
When did this entry get added? I have no idea where that numeric value
would have come from. It's not a valid horde 3 value, nor a valid
horde 4 value for the addressbooks pref.
> mysql> select * from horde_prefs where pref_uid = 'martas at lnk.lt'
> and pref_name = 'addressbooks';
> +---------------+------------+--------------+------------+
> | pref_uid | pref_scope | pref_name | pref_value |
> +---------------+------------+--------------+------------+
> | martas at lnk.lt | turba | addressbooks |
> 345 |
> +---------------+------------+--------------+------------+
> 1 row in set (0.00 sec)
>
> Also I'm not sure, but there are other users who have 'addressbooks'
> set to simple numbers from ~250 to ~400.
>
> mysql> select * from horde_prefs where pref_name = 'addressbooks'
> and pref_value LIKE '____';
> +--------------------------+------------+--------------+------------+
> | pref_uid | pref_scope | pref_name | pref_value |
> +--------------------------+------------+--------------+------------+
> | kitokie at lnk.lt | turba | addressbooks |
> 388 |
> | raimonda at lnk.lt | turba | addressbooks |
> 350 |
> | simkus at lnk.lt | turba | addressbooks |
> 330 |
> | daugirdaite at lnk.lt | turba | addressbooks |
> 332 |
>
> ..........
>
> Seems like upgrade task problem to me. No?
Well, the upgrade task wouldn't produce those values. So if it ran,
something went *really* wrong. If it didn't run, those values are
corrupt anyway. You will have to track this down in
Turba_LoginTasks_SystemTask_Upgrade#_upgradeAbookPrefs() with a fresh
set of unupdated data and see what the values are at different points
along the process.
More information about the bugs
mailing list