The following comment has been added to this issue:
Author: Oliver Gries
Created: Tue, 25 Nov 2003 11:57 PM
Body:
Hi,
maybe the priority of this issue should be increased, because if you don't use saveOrUpdate() as the implementation of the ODMG method makePersistent(), how should an object ever be updated??
Because makePersistent() is the only interface method where you can trigger the persistence of an transient AND persistent object.
;-(
Oliver
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-85
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-85
Summary: ODMG: Database.makePersistent() -> saveOrUpdate() inst. of save()
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Assignee:
Reporter: Oliver Gries
Created: Mon, 19 May 2003 12:33 AM
Updated: Tue, 25 Nov 2003 11:57 PM
Environment: n.a.
Description:
Would'nt it be only consistent to wrap Session.saveOrUpdate() in the odmg implementation for the Database.makePersistent() method instead of Session.save() ??
Greetings Oliver
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
