Jump to: navigation, search

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

Line 6: Line 6:
  
 
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.
 +
 +
[2]
 +
 +
The spec says "org.eclipse.persistence.sessions.Project will have a public set/getDefaultTableCreationSuffix accessors to allow setting a default in native EclipseLink projects."
 +
but I don't wee those accessors in the Javadoc. Do they exist? Should they be documented in this topic?

Revision as of 10:31, 3 February 2011

[1]

The following sentences are derived from 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.

[2]

The spec says "org.eclipse.persistence.sessions.Project will have a public set/getDefaultTableCreationSuffix accessors to allow setting a default in native EclipseLink projects." but I don't wee those accessors in the Javadoc. Do they exist? Should they be documented in this topic?