Book a Demo

Author Topic: LastLoadDate vs. LastSaveDate vs. XML datetime  (Read 3791 times)

lubos

  • EA User
  • **
  • Posts: 101
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
LastLoadDate vs. LastSaveDate vs. XML datetime
« on: January 16, 2009, 07:59:21 pm »
Hello,
we use a Clearcase to version our models.
so we have some parts of model stored/versioned in XML files.

Since we share some of the model parts between more models (we import corresponding XML into more models) we try to solve the problem of correct synchronization of models.

It seems to me that a possible way how to handle it is to compare the times mentioned in the headline.
An my expectations are as follows:

*) package.LastLoadDate is the time of the latest checkout
*) package.LastSaveDate is the the time of the latest checkin
*) Datetime of the XML file is +- the same as the package.LastSaveDate

BUT the datetime of the XML file differs of LastSaveDate a lot (a couple of months for example)

So my question is what do this times mean and how to use them to find out model parts that have to be updated (Get Latest ...) ????

Thanks for any hints

lubos

  • EA User
  • **
  • Posts: 101
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: LastLoadDate vs. LastSaveDate vs. XML datetime
« Reply #1 on: January 16, 2009, 08:06:44 pm »
an example for illustration:

XML: 31.10.2008 13:01 & Model Load: 17.12.2008 11:38 & Model Save: 17.12.2008 11:37

whis is strange for me because

Load > Save
XML < Save  (a lot)


lubos

  • EA User
  • **
  • Posts: 101
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: LastLoadDate vs. LastSaveDate vs. XML datetime
« Reply #2 on: January 21, 2009, 11:37:16 pm »
an answer from Sparx (for anybody interested):


..... the LastSaveDate is not being updated when the package is sent to version control.

As far as I can tell, this problem is simply due to oversight on our part and it will be rectified as soon as possible.

We should be releasing EA version 7.5 (beta1), build 840, in the next few days.  I expect the fix for this problem will be included in build 841, which should follow shortly afterwards.
« Last Edit: January 21, 2009, 11:38:00 pm by lubos »