Bugzilla – Full Text Bug Listing
| Summary: | Need support for 'non-associative' flag on PLSQLTable interface and plsql-table in XML | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | David McCann <david.mccann> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |
Created attachment 210522 [details] Potential fix. PL/SQL collections can be either associative (INDEX BY clause) or non-associative. At runtime we generate anonymous PL/SQL (in PLSQLStoredProcedureCall) and need to know which type of collection we are dealing with as the constructors for each are different. The flag should be optional, and default to false.