ok clear. only the tables which do not exist and new columns i guess.
but then is that not working in m5? i think i'm using that. all my
tables are getting created and expanded with my developing.
or is that because of the integration-test which i run?
when there are two options
1) add tabels and sample data with integration-test
2) option 1 and with a deployed war file
i only need option 1 ;)
are we on the same line now :D
tibi
Matt Raible wrote:
On 7/30/07, tibi <[EMAIL PROTECTED]> wrote:
but in which case will you build against your life database??
my usual setup is;
a local developer database on my developer machine
i run mvn jetty:run most times and when i get cluttered test data i run
mvn integration-test te clear everything and check my app.
a build database on the coninuum test server which will be reset every
hour with the sample-data.
my database with life data is on the life server. with its own database.
when i deploy a new war it will not be affected by hbm2ddl
right?
Correct, but if we turn on hibernate.hbm2ddl.auto=update (as a
hibernate property on the sessionFactory), it *will* create the tables
if they don't exist. That's what the initial discussion of this thread
was/is about.
Matt
tibi
Matt Raible wrote:
I'm inclined to leave it *off* by default. Why? Because it's been off
for the last several releases and no one has complained about it. I
also don't want to ship a version of AppFuse that auto-upgrades
database tables w/o developers being aware of it. In most real-world
environment, the database upgrades are handled by DBAs, not
developers.
Matt
On 7/30/07, tibi <[EMAIL PROTECTED]> wrote:
please leave it on by default.
i use it for testing and building.
in deployment its is not in the way as long as you will not build
against your life database.
and it is easier to turn of than on ;)
good luck
tibi
Martin Homik wrote:
As a newbie, I also vote for turning on by default. Once you get familiar
with AppFuse and/or application frameworks, people will figure out how to
turn off the hibernate plugin either be checking the mailing list or by
having a look into the FAQ. The latter is one of my first sources I check
once I get stuck. Therefore, it'll be great to covor common problems in the
FAQ.
Martin
Matt Raible-3 wrote:
What do folks think, should we turn hbm2ddl off by default? Or leave
it on so the database is updated by default, and users have to do the
steps below to turn it off?
Thanks,
Matt
On 1/28/07, Matt Raible <[EMAIL PROTECTED]> wrote:
It's on by default in the base sessionFactory definition of AppFuse.
Now that the hibernate3 plugin is working as expected, it might be a
good idea to turn it off again. In the meantime, you should be able
to either 1) create a src/main/resources/hibernate.properties with:
hibernate.hbm2ddl.auto=false
Or 2), you can define a bean definition as follows:
<bean class="org.appfuse.dao.spring.HibernateExtensionPostProcessor">
<property name="hibernateProperties">
<value>hibernate.hbm2ddl.auto=false</value>
</property>
</bean>
On 1/28/07, Jaime Geovane Marcondes <[EMAIL PROTECTED]> wrote:
Hi.
We are migrating a old webapp from webwork to appfuse2.0-M2, and it
speeding
up the development process.
Now we want to deploy the project, but when the project initializes, he
executes hibernate:hbm2ddl goal. How we can turn this off ?
Thanks!
--
View this message in context:
http://www.nabble.com/Turning-Off-hbm2ddl-tf3133830s2369.html#a8683543
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://raibledesigns.com
--
http://raibledesigns.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
