Bug 129144

Summary: Separate Commits for main objects and child objects
Product: [Retired] Red Hat Network Reporter: Ryan Bloom <rbb>
Component: RHN/R&DAssignee: Ryan Bloom <rbb>
Status: CLOSED CURRENTRELEASE QA Contact: Fanny Augustin <fmoquete>
Severity: medium Docs Contact:
Priority: medium    
Version: RHN Devel   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-09-07 17:37:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 125080    

Description Ryan Bloom 2004-08-04 14:11:34 UTC 
The new rules that we need to conform to:

A commit always saves 1 and only 1 object.
A lookup always loads the requested object (if available) and may also
load other objects for performance reasons.

Basically, calling commit on the UserFactory should only commit the
User, not the User's addresses or any other business object in the
User.  Calling addRole on a User should update the roles in the DB
directly, not rely on calling commit to do so.  This is the model we
will follow everywhere.
Comment 1 Ryan Bloom 2004-09-07 17:37:56 UTC 
This has been done now.  This was done for two reasons:  1)  To follow
our proscribed model, and 2) for performance reasons.