Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Development/DBWS/NamingConventionTransformer"

(DBWS utility enhancements)
Line 14: Line 14:
 
|}
 
|}
  
== DBWS utility enhancements ==
+
== DBWS utility enhancement: Naming convention of generated schema types ==
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=234677 bug 234677] The DBWSBuilder utility should allow user to alter names of the generated schema type. The algorithm the DBWSBuilder utility uses two very simple rules:
+
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=234677 bug 234677] <br/>
** table name ==> translate any characters un-supported by XML <sub>1</sub> ==> to_lowercase ==> add suffix 'Type' ==> top-level complex element type in {{.xsd}} file
+
The DBWSBuilder utility should allow the user to alter the names of the generated schema types. <br/>
** column name ==> translate characters ==> to_lowercase ==> element tag name <sub>2</sub>
+
The algorithm currently in use is very simple:
<sub>1</sub> - same algorithm documented as part of the SQL/X (a.k.a. SQL/XML:2003) specification)
+
* table name ==> translate any characters un-supported by XML<sup>1</sup> ==> to_lowercase ==> add suffix 'Type' ==> top-level complex element type in <tt>.xsd</tt> file
<sub>2</sub> - All columns expressed as XML elements;
+
* column name ==> translate characters ==> to_lowercase ==> element tag name<sup>2</sup>
 +
<sup>1</sup> - same algorithm documented as part of the SQL/X specification (a.k.a. ISO/IEC 9075-14:2003 Information technology -- Database languages -- SQL -- Part 14: XML-Related Specifications) <br/>
 +
<sup>2</sup> - All columns expressed as XML elements

Revision as of 12:35, 11 September 2008

DBWS Schema Naming Convention Transformers

Document History

Date Author Version Description & Notes
080911 Mike Norman 1.0

DBWS utility enhancement: Naming convention of generated schema types

bug 234677
The DBWSBuilder utility should allow the user to alter the names of the generated schema types.
The algorithm currently in use is very simple:

  • table name ==> translate any characters un-supported by XML1 ==> to_lowercase ==> add suffix 'Type' ==> top-level complex element type in .xsd file
  • column name ==> translate characters ==> to_lowercase ==> element tag name2

1 - same algorithm documented as part of the SQL/X specification (a.k.a. ISO/IEC 9075-14:2003 Information technology -- Database languages -- SQL -- Part 14: XML-Related Specifications)
2 - All columns expressed as XML elements

Back to the top