Calendar continuously upgrading on startup...

View: New views
2 Messages — Rating Filter:   Alert me  

Calendar continuously upgrading on startup...

by Tony Atkins-2 :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message

Hello:

I'm working to test the QA instance of Collab with 2.5beta2, and am noticing that the calendar conversion is taking place every time I start up Sakai.  I do have sak11204.forceupgrade set to false in sakai.properties.

Anyway, is anyone seeing anything like this with 2.5beta2?

Thanks,


Tony
--

<tony.atkins@...>
Software Development Manager
UHI Millennium Institute


----------------------
This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org/portal) from the DG: Development (a.k.a. sakai-dev) site.
You can modify how you receive notifications at My Workspace > Preferences.


Parent Message unknown Re: Calendar continuously upgrading on startup...

by Tony Atkins-2 :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message

There were 5 records from 2003 with null start and end ranges.  I assigned values based on nearby neighbors and the calendar migration didn't run on startup:

INFO: init(): caching: false (2007-12-25 09:02:26,960 main_org.sakaiproject.calendar.impl.BaseCalendarService)
INFO: SAK-11204: Calendar Conversion Complete  (2007-12-25 09:02:26,965 main_org.sakaiproject.calendar.impl.SAK11204Fix)
INFO: init(): tables: CALENDAR_CALENDAR CALENDAR_EVENT locks-in-db: false (2007-12-25 09:02:26,965 main_org.sakaiproject.calendar.impl.DbCalendarService)

Thanks to Stephen for pointing out the solution.


Tony

>>> On Tue, Jan 29, 2008 at  9:03 AM, "Stephen Marquard"
<stephen.marquard@...> wrote:

> We're not seeing that. Maybe it's not converting correctly or something. Try
> this and see what you get:
>
> mysql> select * from CALENDAR_EVENT WHERE RANGE_START IS NULL;
> Empty set (0.04 sec)
>
> mysql> select * from CALENDAR_EVENT WHERE RANGE_END IS NULL;
> Empty set (0.02 sec)
>
> (on our db there aren't any nulls in those fields).
>
> Cheers
> Stephen
>
> Stephen Marquard, Learning Technologies Co-ordinator
> Centre for Educational Technology, University of Cape Town
> http://www.cet.uct.ac.za
> Email/IM/XMPP: stephen.marquard@...
> Phone: +27-21-650-5037 Cell: +27-83-500-5290
>
>
>>>> "Tony Atkins" <Tony.Atkins@...> 2008/01/29 10:55 AM >>>
> This seems to the be the key:
>
> INFO: SAK-11204: Migration check, there are null range fields  (2007-12-24
> 20:21:37,072 main_org.sakaiproject.calendar.impl.SAK11204Fix)
> INFO: SAK-11204: Converting Calendar 1 of 8191 (2007-12-24 20:21:42,315
> main_org.sakaiproject.calendar.impl.SAK11204Fix)
> INFO: SAK-11204: Converting Calendar 2 of 8191 (2007-12-24 20:21:42,326
> main_org.sakaiproject.calendar.impl.SAK11204Fix)
>
> I ran the 2.4->2.5 migration for MySQL ahead of the first startup.
>
>
> Tony
>
>>>> On Tue, Jan 29, 2008 at  8:37 AM, "Stephen Marquard"
> <stephen.marquard@...> wrote:
>> Hi Tony,
>>
>> What are you seeing in the logs?
>>
>> Cheers
>> Stephen
>>
>> Stephen Marquard, Learning Technologies Co-ordinator
>> Centre for Educational Technology, University of Cape Town
>> http://www.cet.uct.ac.za 
>> Email/IM/XMPP: stephen.marquard@...
>> Phone: +27-21-650-5037 Cell: +27-83-500-5290
>>
>>
>>>>> "Tony Atkins" <Tony.Atkins@...> 2008/01/28 11:35 PM >>>
>> Hello:
>>
>> I'm working to test the QA instance of Collab with 2.5beta2, and am noticing
>
>> that the calendar conversion is taking place every time I start up Sakai.  I
>
>> do have sak11204.forceupgrade set to false in sakai.properties.
>>
>> Anyway, is anyone seeing anything like this with 2.5beta2?
>>
>> Thanks,
>>
>>
>> Tony

----------------------
This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org/portal) from the DG: Development (a.k.a. sakai-dev) site.
You can modify how you receive notifications at My Workspace > Preferences.