Horde DB changes from 2.1 to 3-beta? (was Re: [imp] Re: turba-h3-2.0 bug/problem)

[Steve Lidie]

On Nov 16, 2004, at 2:07 PM, Chuck Hagenbuch wrote:
>
> For this particular case, I'd just discard the old preferences. Last 
> login is
> transitory information; it won't hurt anything to have people get a 
> Last Login:
> Never on their first login to the new version.

True.  But actually I would always get "Never", no matter how many 
times I logged in.  Only after if changed pref_scope from 'imp' to 
horde' did that feature work.  Someone was confused by having the same 
pref_name with two scopes.

So, what I worried about is what else might I be 
"converting/moving/copying", in error, that will be a problem down the 
line?  Everything else *seems* to be working ;)  If you implementors 
can't think of anything major, then I'm happy.  Right now I use DBI to 
convert horde_prefs, horde_users and turba_objects:

[root at imp4 4.0]# ./imp3.1.turb1.1-TO-imp4.0.turba2.0
Tue Nov 16 14:35:30 2004 : connecting to the old DB on xyxxy.plugh.edu
Tue Nov 16 14:35:30 2004 : connecting to the new DB on localhost
Tue Nov 16 14:35:30 2004 :   preparing horde_prefs SQL
Tue Nov 16 14:35:31 2004 :     deleting contents of horde_prefs from 
localhost
Tue Nov 16 14:35:31 2004 :     migrating horde_prefs
Tue Nov 16 14:36:14 2004 :   59979 rows in horde_prefs
Tue Nov 16 14:36:14 2004 :   preparing horde_users SQL
Tue Nov 16 14:36:14 2004 :     deleting contents of horde_users from 
localhost
Tue Nov 16 14:36:14 2004 :     migrating horde_users
Tue Nov 16 14:36:14 2004 :   0 rows in horde_users
Tue Nov 16 14:36:14 2004 :   preparing turba_objects SQL
Tue Nov 16 14:36:16 2004 :     deleting contents of turba_objects from 
localhost
Tue Nov 16 14:36:16 2004 :     migrating turba_objects
Tue Nov 16 14:37:40 2004 :   77575 rows in turba_objects
Tue Nov 16 14:37:40 2004 : disconnecting
[root at imp4 4.0]#

Steve