John, The only problem with that logic is that the server has always been in control of the create/modify date/time. To verify your scenario, you could quickly swap out the api that your java program is running for a 7.6.04 SP4, or even an 8.1 jar file for testing....
On Wed, Jun 12, 2013 at 9:50 AM, John Sundberg < john.sundb...@kineticdata.com> wrote: > ** > > We have recently seen a sporadic issue with the 8.0 Java API against a > 7.6.4 server… > > The issue is -- a record is created at 2013-06-10T12:00:00 … (call this > 123456789) > > However > > when the record gets updated… > > The log shows > > update T1 where c4 <= 123456788 …… > > (Notice - the one second less than the create time) > > So I think what is happening is that the client library is somehow losing > a second (off by one error???) on the update. So - the update fails with > "This record has been updated since you last touched it"… > > However -- if you drop in the 7.6.4 client library -- it works fine. > > > So … 8.0 client bug ??? or something else? > > > > > > -John > > > > > -- > > *John Sundberg* > Kinetic Data, Inc. > "Your Business. Your Process." > > 651-556-0930 I john.sundb...@kineticdata.com > www.kineticdata.com I community.kineticdata.com > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
