Bug 129144 – Separate Commits for main objects and child objects

Bug 129144 - Separate Commits for main objects and child objects

Summary:	Separate Commits for main objects and child objects

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Network
Classification:	Red Hat
Component:	RHN/R&D (Show other bugs)
Sub Component:
Version:	RHN Devel
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Ryan Bloom
QA Contact:	Fanny Augustin
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	rhnMilestone1
	Show dependency tree / graph

Reported:	2004-08-04 10:11 EDT by Ryan Bloom
Modified:	2007-04-18 13:10 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-09-07 13:37:56 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Ryan Bloom 2004-08-04 10:11:34 EDT

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 13:37:56 EDT

This has been done now.  This was done for two reasons:  1)  To follow
our proscribed model, and 2) for performance reasons.

Note You need to log in before you can comment on or make changes to this bug.