[
https://issues.apache.org/jira/browse/OPENJPA-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abe White resolved OPENJPA-214.
-------------------------------
Resolution: Fixed
Assignee: (was: Abe White)
Support float/Float and double/Double primary key fields in single-field
identity handling. Fixed in revision 527648.
> Need to support floating point primary keys
> -------------------------------------------
>
> Key: OPENJPA-214
> URL: https://issues.apache.org/jira/browse/OPENJPA-214
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 0.9.7
> Reporter: Kevin Sutter
> Fix For: 0.9.8
>
>
> Dain first reported this problem on the dev mailing list:
> http://www.nabble.com/Float-primary-key--tf3557137.html
> >My response:
> >Okay, I looked at the spec a bit closer and it looks like we need to allow
> >for floats as primary keys:
> >"The primary key (or field or property of a composite primary key) should be
> >one of the following types:
> >any Java primitive type; any primitive wrapper type; java.lang.String;
> >java.util.Date;
> >java.sql.Date. In general, however, approximate numeric types (e.g.,
> >floating point types) should
> >never be used in primary keys."
> >Although the spec clearly recommends against the use of floating points,
> >floats are a primitive type (or the Float wrapper) and need to be allowed.
> >With no >special "AllowStupidApproximatePrimaryKeys" flag. :-)
> >Am I trying to read too much into the spec or Dain's request? This seems to
> >be something that we need to support.
> >>Abe's response:
> >>Given the spec section you quoted, you're definitely right. It's something
> >>we need to support.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
