Home › Forums › Developers › General developer's discussion ›

1.8 Schedule upgrade

Submitted by Ben_Charlton on Sat, 13/06/2015 - 13:01
in

Following routine upgrade procedures this was how our main schedule appeared...

Now the result from our live database shows 

  63 date 1970-01-01 18:00:00.0 EST endTime
  63 boolean true inputWeight
  63 int 100 maximumSlots
  63 int 15 slotSize
  63 string MINUTES slotUnit
  63 date 1970-01-01 08:00:00.0 EST startTime

 

After the upgrade nothing has changed. Upgraded data shows

63 date 1970-01-01 18:00:00.0 EST endTime
63 boolean true inputWeight
63 int 100 maximumSlots
63 int 15 slotSize
63 string MINUTES slotUnit
63 date 1970-01-01 08:00:00.0 EST startTime

Our shedule is suppose to run from 8am until 6pm...so the figures look right ..not sure EST is correct tho

The OS is set to AEST BRISBANE no DST

The other schedules have a similar problem...BUT all appointments have copied over at the correct times.

  95601 0 act.customerAppointment 1.0 d3de16c6-0bed-11e5-a2dd-538b466c1501 Appointment   1   2015-06-13 10:30:00 2015-06-13 10:45:00 VACCINATION PENDING

See here who the info does not contain the EST ...and is set for a correct date rather than the value for the schedule.

 

 

 

 

‹ Updated Templating and Invoice Formats Strike Through on schedule view once completed ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: 1.8 Schedule upgrade

Submitted by tanderson on Sat, 13/06/2015 - 15:06.

Possibly related to: http://www.openvpms.org/forum/wst-timezone-issue

In 1.7 and later, all date/times stored in details nodes are serialized to strings as sql-timestamps. To correct the issue, you can:

  • update the times via the UI to get them to be stored without timezones. You may have to adjust them to a different time first in order for them to save
  • change the timezones as per http://www.openvpms.org/forum/wst-timezone-issue
     
  • use SQL to change details nodes with type "date" to "sql-timestamp", and remove timezone information

Re: 1.8 Schedule upgrade

Submitted by Ben_Charlton on Tue, 16/06/2015 - 09:53.

Yep that will solve my issue however shouldnt we attempt to include this in the migration...? or atleast check for the issue?

 

Regards
 
Ben 
OpenVPMS Installer and Helper 
Ph: +61423044823 
Email: info[at]charltonit.com[dot]au

Re: 1.8 Schedule upgrade

Submitted by tanderson on Wed, 17/06/2015 - 10:59.

Raised as https://openvpms.atlassian.net/browse/OVPMS-1627

Regards,

-Tim

Re: 1.8 Schedule upgrade

Submitted by Ben_Charlton on Tue, 16/06/2015 - 10:02.

BTW my solution was to update the schedules in my 1.7 system then recopy the test data base...

This avoids the need for sql changes.  It will make Openvpms change the dates to sql-timestamps 

Regards
 
Ben 
OpenVPMS Installer and Helper 
Ph: +61423044823 
Email: info[at]charltonit.com[dot]au
Syndicate content