Fwd: RE: ingo::upgrade::problem

[Jan Schneider]

----- Weitergeleitete Nachricht von idcommunication@... -----
     Datum: Wed, 3 Jun 2009 13:50:03 +0200
       Von: Rafael Berez <idcommunication@...>
   Betreff: RE: [ingo] ingo::upgrade::problem
        An: jan@...

Hello,

because we have over 30.000 webmail users, we split the whole user list in blocs containing 100 users.
for each bloc we got an output like:

Converting filters for user: userxxx.....done

seems ok for me...

we have the following sql tables:

| horde_alarms          
| horde_cache                
| horde_categories          
| horde_datatree            
| horde_datatree_attributes  
| horde_datatree_seq        
| horde_groups              
| horde_groups_members      
| horde_groups_seq          
| horde_histories          
| horde_histories_seq        
| horde_locks                
| horde_perms              
| horde_perms_seq            
| horde_prefs              
| horde_syncml_anchors      
| horde_syncml_map          
| horde_tokens              
| horde_users                
| horde_vfs                
| imp_sentmail              
| ingo_forwards              
| ingo_lists                
| ingo_rules                
| ingo_rules_seq            
| ingo_shares              
| ingo_shares_groups      
| ingo_shares_users          
| ingo_spam                
| ingo_vacations          
| turba_objects  

ingo_vacations for example looks like this (for every user):

mysql> select * from ingo_vacations where vacation_owner='teststudi';
+----------------+--------------------+------------------+-----------------+---------------+----------------+--------------+-------------------+----------------------+
| vacation_owner | vacation_addresses | vacation_subject | vacation_reason | vacation_days | vacation_start | vacation_end | vacation_excludes | vacation_ignorelists |
+----------------+--------------------+------------------+-----------------+---------------+----------------+--------------+-------------------+----------------------+
| teststudi      |                    |                  |                 |             7 |              0 |            0 |                   |                    1 |
+----------------+--------------------+------------------+-----------------+---------------+----------------+--------------+-------------------+----------------------+

the already existing rules are still in horde_prefs:
...
| teststudi | ingo       | vacation                | a:6:{s:9:"addresses";a:2:{i:0;s:25:"sm-test@...";i:1;s:27:"teststudi@...";}s:4:"days";s:1:"7";s:8:"excludes";a:0:{}s:10:"ignorelist";b:1;s:6:"reason";s:8:"weil weg";s:7:"subject";s:12:"bin nicht da";}  
...

thanks

Rafael

> Date: Tue, 2 Jun 2009 18:30:19 +0200
> From: jan@...
> To: ingo@...
> Subject: Re: [ingo] ingo::upgrade::problem
>
> Zitat von Rafael Berez <idcommunication@...>:
>
> >
> > Hello list,
> >
> > we are upgrading ingo from v. 1.1 to 1.2.1.
> > we want to use the new SQL table as a storage backend for our filter rules.
> > we encountered the following problem:
> >
> > after running the provided PHP script "convert_prefs_to_sql.php",  
> > the already existing filter rules remain in the
> > horde_prefs table but newly created filter rules are written to the  
> > corresponding tables (e.g. ingo_forwards).
> >
> > Sould already existing filter rules not be migrated to the new tables too??
>
> Yes, that's the purpose of that script. What's the output of the script?
>
> Jan.
>
> --
> Do you need professional PHP or Horde consulting?
> http://horde.org/consulting/

-------------------------
check out the rest of the Windows Live™.More than mail–Windows Live™ goes way beyond your inbox. More than messages

----- Ende der weitergeleiteten Nachricht -----

Jan.

--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/

--
Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: ingo-unsubscribe@...

[Patrick Boutilier]

On 06/05/2009 08:59 AM, Jan Schneider wrote:

>
> ----- Weitergeleitete Nachricht von idcommunication@... -----
>       Datum: Wed, 3 Jun 2009 13:50:03 +0200
>         Von: Rafael Berez<idcommunication@...>
>     Betreff: RE: [ingo] ingo::upgrade::problem
>          An: jan@...
>
> Hello,
>
> because we have over 30.000 webmail users, we split the whole user list in blocs containing 100 users.
> for each bloc we got an output like:
>
> Converting filters for user: userxxx.....done
>
> seems ok for me...
>
> we have the following sql tables:
>
> | horde_alarms
> | horde_cache
> | horde_categories
> | horde_datatree
> | horde_datatree_attributes
> | horde_datatree_seq
> | horde_groups
> | horde_groups_members
> | horde_groups_seq
> | horde_histories
> | horde_histories_seq
> | horde_locks
> | horde_perms
> | horde_perms_seq
> | horde_prefs
> | horde_syncml_anchors
> | horde_syncml_map
> | horde_tokens
> | horde_users
> | horde_vfs
> | imp_sentmail
> | ingo_forwards
> | ingo_lists
> | ingo_rules
> | ingo_rules_seq
> | ingo_shares
> | ingo_shares_groups
> | ingo_shares_users
> | ingo_spam
> | ingo_vacations
> | turba_objects
>
> ingo_vacations for example looks like this (for every user):
>
> mysql>  select * from ingo_vacations where vacation_owner='teststudi';
> +----------------+--------------------+------------------+-----------------+---------------+----------------+--------------+-------------------+----------------------+
> | vacation_owner | vacation_addresses | vacation_subject | vacation_reason | vacation_days | vacation_start | vacation_end | vacation_excludes | vacation_ignorelists |
> +----------------+--------------------+------------------+-----------------+---------------+----------------+--------------+-------------------+----------------------+
> | teststudi      |                    |                  |                 |             7 |              0 |            0 |                   |                    1 |
> +----------------+--------------------+------------------+-----------------+---------------+----------------+--------------+-------------------+----------------------+
>
> the already existing rules are still in horde_prefs:

Script doesn't clean out horde_prefs. You can try something like this
(test on a test system first).


DELETE FROM `horde_prefs` WHERE pref_scope='ingo' and
(pref_name='whitelist' or pref_name='blacklist' or pref_name='rules')

> ...
> | teststudi | ingo       | vacation                | a:6:{s:9:"addresses";a:2:{i:0;s:25:"sm-test@...";i:1;s:27:"teststudi@...";}s:4:"days";s:1:"7";s:8:"excludes";a:0:{}s:10:"ignorelist";b:1;s:6:"reason";s:8:"weil weg";s:7:"subject";s:12:"bin nicht da";}
> ...
>
> thanks
>
> Rafael
>
>> Date: Tue, 2 Jun 2009 18:30:19 +0200
>> From: jan@...
>> To: ingo@...
>> Subject: Re: [ingo] ingo::upgrade::problem
>>
>> Zitat von Rafael Berez<idcommunication@...>:
>>
>>> Hello list,
>>>
>>> we are upgrading ingo from v. 1.1 to 1.2.1.
>>> we want to use the new SQL table as a storage backend for our filter rules.
>>> we encountered the following problem:
>>>
>>> after running the provided PHP script "convert_prefs_to_sql.php",
>>> the already existing filter rules remain in the
>>> horde_prefs table but newly created filter rules are written to the
>>> corresponding tables (e.g. ingo_forwards).
>>>
>>> Sould already existing filter rules not be migrated to the new tables too??
>> Yes, that's the purpose of that script. What's the output of the script?
>>
>> Jan.
>>
>> --
>> Do you need professional PHP or Horde consulting?
>> http://horde.org/consulting/
>
> -------------------------
> check out the rest of the Windows Live™.More than mail–Windows Live™ goes way beyond your inbox. More than messages
>
> ----- Ende der weitergeleiteten Nachricht -----
>
> Jan.
>
>
>
> ------------------------------------------------------------------------
>
> --
> Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: ingo-unsubscribe@...

[boutilpj.vcf]

---

begin:vcard
fn:Patrick Boutilier
n:Boutilier;Patrick
org:;Nova Scotia Department of Education
adr:;;2021 Brunswick Street;Halifax;NS;B3K 2Y5;Canada
email;internet:boutilpj@...
title:WAN Communications Specialist
tel;work:902-424-6800
tel;fax:[phone]
version:2.1
end:vcard

---

--
Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: ingo-unsubscribe@...