| Summary: | Add sparse merge/FetchGroup handling to DBWS Update operation | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Mike Norman <michael.norman> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | eclipselink.dbws-inbox | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 316996 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
Created attachment 177343 [details]
change UpdateOperation to do sparse merge
Fixed in SVN revision: 8167 still todo - update wiki The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |
{follow-on bug now that core Dynamic Persistence supports sparse merge} Generate XSD a bit differently: - unless there is a PK/Unique constraint, all elements/attributes are optional - add sparse merge FetchGroup handling to o.e.p.internal.xr.UpdateOperations