Bug 269368 - Change tracking using backup clone should postpone backup clone creation
Summary: Change tracking using backup clone should postpone backup clone creation
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-19 10:25 EDT by Sebastien Tardif CLA
Modified: 2022-06-09 10:09 EDT (History)
1 user (show)

See Also:

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

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastien Tardif CLA 2009-03-19 10:25:41 EDT 
Change tracking using backup clone should postpone backup clone creation. Since EclipseLink will generate StackOverflow if object are not cached at all in session cache, we can assume all objects has an instance in session cache. So backup clone equal session cache in most cases. So to avoid creating unneeded backup clone, backup clone creation should be postponed and done lazilly when ever the session cache instance is modified and an outstanding UOW has requested a backup clone for its change tracking.
Comment 1 Eclipse Webmaster CLA 2022-06-09 10:09:00 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink