[kronolith] No Data after Migration

[Simon Brereton]

> -----Original Message-----
> From: Michael J Rubinsky [mailto:mrubinsk at horde.org]
> Simon Brereton <simon.brereton at dada.net> wrote:
> 
> >> -----Original Message-----
> >> From: kronolith-bounces at lists.horde.org [mailto:kronolith-
> >> bounces at lists.horde.org] On Behalf Of Jan Schneider Zitat von
> Simon
> >> Brereton <simon.brereton at dada.net>:
> >>
> >> >> -----Original Message-----
> >> >> From: kronolith-bounces at lists.horde.org [mailto:kronolith-
> >> >> bounces at lists.horde.org] On Behalf Of Simon Brereton After
> >> installing
> >> >> Kronolith 3.0.1 on a clean machine (with Horde 4.0.1), I
> attempted
> >> to
> >> >> migrate the data from the hold Horde 3 install like this:
> >> >>
> >> >>
> >> >> Import the horde3 DB and give permissions to the local horde
> user
> >> to
> >> >> use it.
> >> >>
> >> >> mysql -u root -p < /donald/root/horde3.datestamp.sql mysql -u
> root
> >> -p
> >> >> -e "grant all privileges on horde3.* to 'horde'@'localhost'
> >> >> identified by 'xxxxxxxx';”
> >> >> mysql -u root -p
> >> >> use horde;
> >> >> update kronolith_events set
> >> event_creator_id=lower(event_creator_id);
> >> >>
> >> >>
> >> >> In the Horde Configuration tab changed from the clean horde4 DB
> to
> >> >> the imported one.
> >> >>
> >> >> Horde Configuration – Database
> >> >> 	Called the DB horde3 (was previously horde)
> >> >>
> >> >> Saved the configuration and ran Update DB schema's for all apps
> >> which
> >> >> worked.  I think this called /usr/bin/horde-db-migrate
> >> >>
> >> >> After that, I dumped the clean (and empty) DB horde and renamed
> >> >> horde3 (the old and now updated one) to horde4.  Then I went
> back
> >> to
> >> >> the Horde Configuration tab and changed the name:
> >> >>
> >> >> Horde Configuration – Database
> >> >> 	Called the DB horde4 (was previously horde3)
> >> >>
> >> >> Now, my address books are fine and have all the data, but the
> >> >> calendar data seems to be missing.  However, if I use mysql or
> >> >> phpmyadmin I see the kronolith.events has all the events in it.
> >> But
> >> >> these are not displaying in the calendar.
> >> >>
> >> >> Creating, editing and deleting new events doesn't seem to be a
> >> >> problem.
> >> >>
> >> >> Have I missed anything (read done something stupid) again?
> >> >
> >> >
> >> > I think I've found it.  In the old schema the calendar_id was
> the
> >> same
> >> > as the username/email address.  The new code uses a 22 char
> >> > alphanumeric mixed-case string...
> >> >
> >> > Is that a hash of something so that I can just update that
> column?
> >>
> >> No, it's just a random hash, but such hashes were used in
> Kronolith 2
> >> too, for any calendars but your default calendar.
> >
> >Right - but right now, that hash is showing up as the default
> calendar.
> >
> >To bring back the calendar data I would have to add a new event to
> each
> >calendar, and then replace the current calendar_id (user at domain.com)
> >with the hash. (I've tested it and this works).  However, even with
> my
> >limited user-base I'd rather not do that..  Especially if everyone
> else
> >isn't having this issue.
> 
> It sounds like either something went wrong for you during share
> migration, or maybe your not using the share backend that the data is
> stored in.

Where would I debug that?  When I set up H4 I went with the proposed/recommended option of SQl-NG.

I did just discover (prior to your email) that this hash is also in kronolith_shareng as share_name and that changing share_name to match the share_owner/event_creator_id resolves this issue (although it does mean when you first open the calendar you actually have to tick the calendar to display).  Ultimately when I do this migration in production in two weeks time I can run the sql query update kronolith_sharesng set share_name = share_owner after doing the schema update without a problem, but it seems to a be sticking plaster.

I'm starting to wonder if during the upgrade I would have been better advised to run /usr/bin/horde-db-migrate and not use the update schema's button in the config panel.  Another thread indicated they were essentially the same but Vilius and Andreas used that and don't seem to be having the issues I'm having.

Simon