Broadleaf Commerce Discussion Forums

I have the Heat Clinic demo on a cloud server and when I upload changes and new versions the database gets reset to the original demo data.
What can be done to prevent that from happening ?

If you look in development.properties (in site), you will see the following line:



This tells Hibernate that it should create the database cleanly every startup and drop the data on shutdown.

If you'd like to persist your data, you will want to change it to "create", start up once (to get the initial data in there), shutdown, and then change it to "update".

Subsequent startups will then result in only columns/tables being added if necessary, but your data will remain intact.

You can search the Hibernate documentation for more information on all of the available modes.

I was having this problem before I changed this to say update...
in all occurrences of the project.... all 7 of these statements I changed to say update.
I even went as far to delete the sql files in core/src/sql/**
After 2 months of persistent data one day it erased the database. Its seems that the update and deletion of the SQL still initiated a wipe of my data.

Any thoughts?

That property (hbm2ddl.auto) is the only thing that I know of that could drop the data in your tables. I'm not sure what could be erasing it if in fact you have changed every instance of this property to 'update'.

Yes I did find one that was create but it was commented out plus the SQL files I erased the tables the last time that happened to me.