[hermes] Re: hermes Digest, Vol 117, Issue 1

[Jason M. Felice]

mbox mbarsalou wrote:

>>Message: 2
>>Date: Mon, 11 Apr 2005 07:51:41 -0400
>>From: "Jason M. Felice" <jfelice at cronosys.com>
>>Subject: [hermes] Re: upgrading from an older version to a newer
>>	version
>>To: HERMES <hermes at lists.horde.org>
>>Message-ID: <425A64CD.8050300 at cronosys.com>
>>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>>Barsalou wrote:
>>
>>    
>>
>>> 
>>>
>>>      
>>>
>>In this case, there is a new column "deliverable_id" in the 
>>hermes_timeslices table, but this column can be null.  So you can 
>>probably run an SQL statement like so:
>>
>>INSERT INTO hermes_timeslices ( timeslice_id, clientjob_id, employee_id, 
>>jobtype_id, timeslice_hours, timeslice_rate, timeslice_isbillable, 
>>timeslice_date, timeslice_description, timeslice_note, 
>>timeslice_submitted, timeslice_exported, deliverable_id ) SELECT 
>>timeslice_id, clientjob_id, employee_id, jobtype_id, timeslice_hours, 
>>timeslice_rate, timeslice_isbillable, timeslice_date, 
>>timeslice_description, timeslice_note, timeslice_submitted, 
>>timeslice_exported, NULL AS deliverable_id FROM old_hermes_timeslice_table;
>>
>>Alternately, you can restore the old database and use the upgrade script 
>>in hermes/scripts/upgrade/
>>
>>    
>>
>Jason, this worked for me just fine.  Should we consider adding this as
>a "migration" script?  I'm using CVS 3-30-05 and it didn't seem to be
>there.
>  
>
This particular migration script would only be useful if you'd installed 
a new version from scratch instead of using the existing upgrade 
script.  I *hope* that not many people would do that.  If they do, I 
imagine they would usually have many more problems in other places.

>I'm still working on moving my turba_objects, but that's for another
>list. :)
>  
>

:-)

>Mike B.
>
>  
>


-- 
 Jason M. Felice
 Cronosys, LLC <http://www.cronosys.com/>
 216.221.4600 x302