Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] specify storage engine?

Hi, this sounds like a good enhancement request. For now I would think the only way to change the underlying engine is to restart MySQL after switching to InnoDB from MyISAM and rerun the DDL generation on the first predeploy - making sure that all tables and sequences are dropped. I would have to verify this though on V4 or 5 before it would be helpful.

Here is an example of an SE persistence unit with generic drop and create DDL generation on for Derby in conjunction with sequence generation on all @Id's - for reference only <persistence-unit name="dao.create.tables.derby.client" transaction-type="RESOURCE_LOCAL">
<property name="javax.persistence.jdbc.driver" value="org.apache.derby.jdbc.ClientDriver"/> <property name="" value="Derby"/> <property name="javax.persistence.jdbc.url" value="jdbc:derby://;create=true"/>
           <property name="javax.persistence.jdbc.user" value="APP"/>
           <property name="javax.persistence.jdbc.password" value="APP"/>
<property name="eclipselink.logging.level" value="ALL"/> <property name="eclipselink.ddl-generation" value="drop-and-create-tables"/> <property name="eclipselink.ddl-generation.output-mode" value="database"/> <!-- or "both" for sql output as well-->
</persistence-unit> See

   thank you

Andreas Kollegger wrote:
Is there a configuration property in persistence.xml that can be used to change the storage engine used for generated tables? For instance, innodb instead of MyISAM.


eclipselink-users mailing list

Back to the top