[kronolith] I missed running the UTC script. Will it hurt to run it after I have old data and new data mixed together?

[Jan Schneider]

Zitat von gimili <gimili17 at gmail.com>:

> On 6/01/11 2:58 PM, Jan Schneider wrote:
>>
>> Zitat von gimili <gimili17 at gmail.com>:
>>
>>> On 6/01/11 1:50 PM, Jan Schneider wrote:
>>>>
>>>> Zitat von gimili <gimili17 at gmail.com>:
>>>>
>>>>> I missed running the UTC script.  Will it hurt to run it after I have
>>>>> old data and new data mixed together?
>>>>
>>>> If you use new and old data together, and have UTC enabled in the
>>>> configuration, your data is already completely messed up.
>>>
>>> Thanks Jan for the info.  Unfortunately this is the case.  I  
>>> checked and I have "Store the dates in UTC format" ticked off.   
>>> Could you describe completely messed up?  Everything seems to be  
>>> working ok.  Will the new data be ok?  Any suggestions?
>>
>> The old data is stored in the users' local timezone, the new data  
>> is stored in UTC format. Unless you happen to live in the GMT  
>> timezone and in a country that doesn't have DST, all your old  
>> events will be off by your (users') timezone's offset.
>>
>> You can change the conversion script to look up each event's  
>> history and only update it if the modification/creation date is  
>> before the time you did the migration.
>>
>> Jan.
>>
> So if I am understanding correctly all the new events should be ok?

Yes.

> I am not skilled enough to change the conversion script but if going  
> forward is ok that is acceptable.  Perhaps ticking the UTC checkbox  
> should trigger a warning or the description for the checkbox should  
> include a warning regarding ramifications.  It seems more dangerous  
> than the other kronolith configuration items.  Thanks again Jan for  
> your help and advice.

I added a warning to the configuration screen.

Jan.

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