• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

hbm2ddl it's not recommended for production

 
Moayad Abu Jaber
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,
recently I tried to used database.hibernate.hbm2ddl in hibernate but it's not recommended for production.
I'm now try to used this option to help for create the schema just for one time. FYI all the DB configuration I use it in properties file and place it in spring config.

thanks in advanced


 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What's your question? Are you asking if you should use hbm2ddl in production?
 
Moayad Abu Jaber
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I need to use it for production but in my application, Wanna use it Independently to create DB for the first time as Patch.
in the same time I wanna use the same configuration I used it in my application describe it above



thanks
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
And your question is can you do this? Yes, if you have to.


 
Scott Patterson
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Why is hbm2ddl not recommended for production? Data issue such as adding a not null column to a populated table? or is there a greater issue?

thanks,
sbp
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My guess is because creating your data model from a code generation tool is not going to give you a decent database. There will be a whole bunch of extra configuration (i.e. the stuff that is usually the realm of the DBA) that will be missed. It is very much a tool to aid development not speed up release deployment.
 
Scott Patterson
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No doubt you would not want to use it to create large OLTP databases. Assuming the limitations are around database configuration, I may well use it for some special tasks. For example we have a master reference repository system that publishes reference tables that are "available" to be picked up by the consuming systems. The structures are quite simple and the data is read once as the "accept" process moves the values to the live location. The live database is carefully controlled and configured, however, there is no value in having the "available" highly controlled.

This assumes that database configuration is the only issue.


regards,
sbp
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic