Difference between revisions of "Talk:EclipseLink/UserGuide/JPA/Advanced JPA Development/Schema Generation/Appending strings to CREATE TABLE statements"

From Eclipsepedia

Jump to: navigation, search
(New page: [1] The following paragraph from the topic is derived from {https://bugs.eclipse.org/bugs/show_bug.cgi?id=214519 Bug 214519]. (In fact it seems to be the reason for submitting the bug.) "...)
 
Line 1: Line 1:
 
[1]
 
[1]
The following paragraph from the topic is derived from {https://bugs.eclipse.org/bugs/show_bug.cgi?id=214519 Bug 214519]. (In fact it seems to be the reason for submitting the bug.)
 
  
"This can be useful, for example, to create tables that are transactional, by appending <tt>engine=InnoDB</tt> to the end of the CREATE TABLE statement. This specifies that the MySQL InnoDB storage engine will be used."
+
The following sentences are derived from {https://bugs.eclipse.org/bugs/show_bug.cgi?id=214519 Bug 214519]. (In fact it seems to be the reason for submitting the bug.)
 +
 
 +
"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."
  
 
Should I leave that in? It looks like that is the default engine in MySQL 5.5, so maybe it isn't a good example anymore.
 
Should I leave that in? It looks like that is the default engine in MySQL 5.5, so maybe it isn't a good example anymore.

Revision as of 10:27, 3 February 2011

[1]

The following sentences are derived from {https://bugs.eclipse.org/bugs/show_bug.cgi?id=214519 Bug 214519]. (In fact it seems to be the reason for submitting the bug.)

"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."

Should I leave that in? It looks like that is the default engine in MySQL 5.5, so maybe it isn't a good example anymore.