X-Git-Url: http://juplo.de/gitweb/?a=blobdiff_plain;f=src%2Fsite%2Fxhtml%2Fpitfalls.xhtml;h=a8eb5ab7c204aa82106b7d44ee5678fed57cf9ed;hb=2af1ce0850ce7d29966072b750c53c144fb8f295;hp=3d8c616406e1ddd97401d779c806dafc9b8cc0cc;hpb=2ec0af491d992d9c26000f803bbc61fdb1299318;p=hibernate4-maven-plugin diff --git a/src/site/xhtml/pitfalls.xhtml b/src/site/xhtml/pitfalls.xhtml index 3d8c6164..a8eb5ab7 100644 --- a/src/site/xhtml/pitfalls.xhtml +++ b/src/site/xhtml/pitfalls.xhtml @@ -16,20 +16,19 @@
- The default-configuration exports the created schema to the configured
- database.
+ The default-configuration executes the created SQL.
Therefore, it needs a valid database-connection and fails, if none is
available.
- If you do not need to export the created schema to a database,
- you can set the property hibernate.schema.export
to
+ If you do not need the generated SQL to be executed automatically,
+ you can set the property hibernate.schema.execute
to
false
.
This can be achieved with the command-line parameter
- -Dhibernate.schema.export=false
or with the following
+ -Dhibernate.schema.execute=false
or with the following
configuration:
<configuration> - <export>false</export> + <execute>false</execute> </configuration>
But even when no database is to be created, hibernate always needs to know @@ -124,7 +123,7 @@
A quick fix to this problem is, to force - hibernate-maven-plugin to export the schema every time it is running. + hibernate-maven-plugin to generate and execute the SQL every time it is running. But to recreate the database on every testrun may noticeable slow down your development cycle, if you have to wait for slow IO.