Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/UserGuide/JPA/Advanced JPA Development/Schema Generation/Appending strings to CREATE TABLE statements"
| Line 17: | Line 17: | ||
| − | You can append a string to the end of a CREATE TABLE statement when generating a DDL | + | You can append a string to the end of a CREATE TABLE statement when generating a DDL. This can be useful, for example, to create tables that are transactional, by appending <tt>engine=InnoDB</tt> to the end of the creation statement. This specifies that the MySQL InnoDB storage engine will be used. |
| − | + | ||
| − | This can be useful, for example, to create tables that are transactional, by appending <tt>engine=InnoDB</tt> to the end of the | + | |
Appending the string only affects the DDL generation. It does not affect any other runtime behavior. | Appending the string only affects the DDL generation. It does not affect any other runtime behavior. | ||
| − | You can specify strings | + | You can specify strings using persistence unit properties or session properties to apply to every table in that context. Specify strings in <tt>eclipselink-orm.xml</tt> to apply to individual tables. |
Use the persistence unit property <tt>eclipselink.ddl-generation.table-creation-suffix</tt> to append a string, as shown in the example below. | Use the persistence unit property <tt>eclipselink.ddl-generation.table-creation-suffix</tt> to append a string, as shown in the example below. | ||
Revision as of 10:28, 3 February 2011
EclipseLink JPA
| EclipseLink | |
| Website | |
| Download | |
| Community | |
| Mailing List • Forums • IRC • mattermost | |
| Issues | |
| Open • Help Wanted • Bug Day | |
| Contribute | |
| Browse Source |
Key API
Appending Strings to CREATE TABLE Statements
>>>>>> THIS PAGE IS IN PROGRESS. PLEASE SEE DISCUSSION PAGE. <<<<<<
You can append a string to the end of a CREATE TABLE statement when generating a DDL. This can be useful, for example, to create tables that are transactional, by appending engine=InnoDB to the end of the creation statement. This specifies that the MySQL InnoDB storage engine will be used.
Appending the string only affects the DDL generation. It does not affect any other runtime behavior.
You can specify strings using persistence unit properties or session properties to apply to every table in that context. Specify strings in eclipselink-orm.xml to apply to individual tables.
Use the persistence unit property eclipselink.ddl-generation.table-creation-suffix to append a string, as shown in the example below.
Example
Assuming it has an ID annotated, an eclipselink-orm.xml file containing...
<entity class="Comment"> <table name="DDL_COMMENT" creation-suffix="COMMENT='User Comment Table'"/> </entity>
...results in the following creation statement:
CREATE TABLE DDL_COMMENT (ID INTEGER) COMMENT='User Comment Table'
If it is coupled with the following persistence property...
<property name="eclipselink.ddl.default-table-suffix" value="engine=InnoDB"/>
it results in the following creation statement:
CREATE TABLE DDL_COMMENT (ID INTEGER) COMMENT='User Comment Table' engine=InnoDB
