This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 322949 - Add support for ResultSet metadata at design-time for Custom SQL
Summary: Add support for ResultSet metadata at design-time for Custom SQL
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL: http://wiki.eclipse.org/EclipseLink/D...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-17 16:01 EDT by Mike Norman CLA
Modified: 2022-06-09 10:34 EDT (History)
1 user (show)

See Also:

Attachments
add support for design-time schema gen for SQLOperations (61.19 KB, patch)
2010-09-27 14:21 EDT, Mike Norman CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Norman CLA 2010-08-17 16:01:25 EDT 
Normally DBWS processes the metadata for custom SQL stmts at run-time -
the information is returned using SXF (the Simplified XML Format, very much
like a rowset).

If the WHERE clause can be reliably parsed, then at design-time an additional
term (1=0) can be added to ensures that no 'real' data is returned but the
ResultSet should have metadata from which an eclipselink-dbws-schema.xsd file
can be built.

(Alternatively, if the user is presented with a GUI, they can 'eye-ball'
the correct place in the WHERE clause)
Comment 1 Mike Norman CLA 2010-09-27 14:21:45 EDT 
Created attachment 179673 [details]
add support for design-time schema gen for SQLOperations
Comment 2 Mike Norman CLA 2010-09-30 12:08:59 EDT 
see SVN revision: 8268
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:34:51 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink