[Hibernate-issues] [Hibernate-JIRA] Resolved: (HB-496) Version and unsaved-value

[<leg...@at...>]

Message:

   The following issue has been resolved as FIXED.

   Resolver: Gavin King
       Date: Thu, 27 Nov 2003 9:02 AM

I applied the patch, with some adjustments. Didn't add the tests yet though.

Thanks.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-496


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-496
    Summary: Version and unsaved-value
       Type: New Feature

     Status: Resolved
   Priority: Major
 Resolution: FIXED

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1 rc1
   Versions:
             2.1 beta 6

   Assignee: Gavin King
   Reporter: Emmanuel Bernard

    Created: Mon, 24 Nov 2003 11:08 PM
    Updated: Thu, 27 Nov 2003 9:02 AM
Environment: Hibernate CVS head of branchv21 nov 25

Description:
Here is a patch allowing unsaved value for version. This is useful for saveOrUpdate() assigned id and having version as primitive type.

Version unsaved-value can be:
* undefined: let the saveOrUpdate choice to id's unsaved-value
    this is the default to prevent mapping break down primitive type version)
* null: save if version==null, update otherwise
* negative: save if version < 0, update otherwise (allowed for short, int, long only)

Timestamp unsaved-value can be:
* null: I think this is the only needed behavior. I don't know how undefined could be useful.
 




---------------------------------------------------------------------
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