Ticket #1101 (assigned defect)

Opened 4 years ago

Last modified 1 year ago

SaveNewUnchanged not working

Reported by: paul Assigned to: paul (accepted)
Priority: major Milestone: 0.8.3
Component: biz Version:
Keywords: Cc:

Description (Last modified by paul)

I've noticed the following behaviors in SaveNewUnchanged?:

  • If SaveNewUnchanged? is True in both parent and child bizobjs, and a new record is added to child, calling parent.save() will not actually insert the new record into the backend. However, Dabo thinks the job is done because we are no longer prompted to save after that point.
  • If SaveNewUnchanged? is False in the parent bizobj and True in the child, then doing child.new() and parent.save() will not save the child record, but Dabo will indeed keep prompting you that there are changes to save.

Change History

09/13/07 14:29:25 changed by paul

  • description changed.
  • summary changed from SaveNewUnchanged=True in children: records not saved when parent.save() to SaveNewUnchanged not working.

10/20/07 23:37:11 changed by paul

I need to write a test case for this one, to prove my case. Bumping milestone to 0.8.3.

10/20/07 23:37:45 changed by paul

  • milestone changed from 0.8.2 to 0.8.3.

10/26/08 11:32:21 changed by paul

  • owner changed from somebody to paul.
  • status changed from new to assigned.

This may or may not still be an issue. I'll find out and act appropriately.

02/01/11 16:59:17 changed by paul

r6371 adds the promised test case.

I note that with: 

bizMain.SaveNewUnchanged = False
bizChild.SaveNewUnchanged = True
bizChild.new()

bizMain.isAnyChanged() will report False and bizChild.isAnyChanged() will report True. But bizMain.save() will indeed save the new unchanged child record.

So there's a minor inconsistency to note, but the original ticket issue appears to have been resolved already.

I'll leave it open for a while to allow for discussion.