| Summary: | composite ids using sequencing should allow zero | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | James Sutherland <jamesssss> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | Keywords: | performance | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
James Sutherland
Fixed by adding a primaryKeyIdValidations to descriptor that allow id pk field to be configured to have a different validation. All default to the descriptor's IdValidation if set, otherwise project default, otherwise don't allow 0 unless composite, but sequence does allow 0. Created attachment 172613 [details]
patch
Patch also includes some memory test cases. Also enhances error message thrown when id is invalid. Fixed in 2.2 (trunck) and 2.1.1 (2.1) The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |