Version 6.1.0 databaseManager.hasRecordChanges() Behavior

Questions, tips and tricks and techniques for scripting in Servoy

Version 6.1.0 databaseManager.hasRecordChanges() Behavior

Postby kwpsd » Sun Aug 05, 2012 1:43 am

Version: 6.1.0 - build 1418

We use databaseManager.hasRecordChanges() in a form's onHide() event to detect if there are changes to the current record. If changes are detected, we query the user to either save or discard the changes.

In 6.1.0, hasRecordChanges() does not recognize that a field has been changed unless the field has lost focus. This is different behavior from 6.0.7.

In 6.0.7, if the user changes only one field and does not tab out of that field, then closes the form, hasRecordChanges() returns 'true'.

In 6.1.0, if the user changes only one field and does not tab out of that field, then closes the form, hasRecordChanges() returns 'false'.

hasRecordChanges() should detect field changes regardless of the field focus.

In 6.1.0, if hasRecordChanges() does not detect the field change, then our query to save/discard the changes is bypassed.

Has anyone else noticed this change in behavior?
Kim W. Premuda
San Diego, CA USA
User avatar
kwpsd
 
Posts: 606
Joined: Sat Jul 28, 2007 6:59 pm
Location: San Diego, CA USA

Re: Version 6.1.0 databaseManager.hasRecordChanges() Behavio

Postby pbakker » Mon Aug 06, 2012 9:29 am

If this can be easily reproduced, please report in our support system.

Regards,

Paul
pbakker
 
Posts: 2821
Joined: Wed Oct 01, 2003 8:12 pm
Location: Amsterdam, the Netherlands

Re: Version 6.1.0 databaseManager.hasRecordChanges() Behavio

Postby kwpsd » Thu Aug 09, 2012 1:20 am

Problem report with test case: SVY-2830
Kim W. Premuda
San Diego, CA USA
User avatar
kwpsd
 
Posts: 606
Joined: Sat Jul 28, 2007 6:59 pm
Location: San Diego, CA USA

Re: Version 6.1.0 databaseManager.hasRecordChanges() Behavio

Postby lvostinar » Tue Aug 28, 2012 10:07 am

kwpsd wrote:Problem report with test case: SVY-2830


In case sample calling setAutoSave(true) saves outstanding changes so this is why no changes are seen afterwards. The behavior is the same in 6.0.7 and 6.1.1 .
Laurian Vostinar
Servoy
lvostinar
 
Posts: 1049
Joined: Tue Feb 19, 2008 10:53 am

Re: Version 6.1.0 databaseManager.hasRecordChanges() Behavio

Postby Kahuna » Tue Aug 28, 2012 10:50 am

lvostinar wrote:
kwpsd wrote:Problem report with test case: SVY-2830


In case sample calling setAutoSave(true) saves outstanding changes so this is why no changes are seen afterwards. The behavior is the same in 6.0.7 and 6.1.1 .


So is this actually NOT a bug Laurian? The operation works as it did in 6.0.6 and 7? I ask because we have been waiting for this as a bug fix since it was reported before we upgrade to 6.1.
(Servoy Version: 6.0.7 Win XP / 7 - SQL Server 2008 R2)
Ian Cordingley (Kahuna)
Kahuna
 
Posts: 1235
Joined: Thu Oct 26, 2006 1:39 am
Location: 1/2 NE UK 1/2 Olvera Spain

Re: Version 6.1.0 databaseManager.hasRecordChanges() Behavio

Postby lvostinar » Tue Aug 28, 2012 11:24 am

Kahuna wrote:
lvostinar wrote:
kwpsd wrote:Problem report with test case: SVY-2830


In case sample calling setAutoSave(true) saves outstanding changes so this is why no changes are seen afterwards. The behavior is the same in 6.0.7 and 6.1.1 .


So is this actually NOT a bug Laurian? The operation works as it did in 6.0.6 and 7? I ask because we have been waiting for this as a bug fix since it was reported before we upgrade to 6.1.


Yes, is not a bug. However, for 6.1.1 we fixed an issue in similar scenario: https://support.servoy.com/browse/SVY-2760 .
Laurian Vostinar
Servoy
lvostinar
 
Posts: 1049
Joined: Tue Feb 19, 2008 10:53 am


Return to Methods

Who is online

Users browsing this forum: No registered users and 1 guest