wood burning stoves 2.0*
The moose likes EJB and other Java EE Technologies and the fly likes Database initialization and patches Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Database initialization and patches" Watch "Database initialization and patches" New topic
Author

Database initialization and patches

Sven Moschel
Greenhorn

Joined: Oct 13, 2010
Posts: 10
We develop a EJB enterprise application and plan to release that application next year. At the moment we debate how to deliver fix application data and how we could handle patches. With fix application data I mean all data that is necessary to work with the application (Access rights, general configuration data, ...).

Some of our developers thinks the best way to deliver such data are native sql scripts. The other part said the easiest way to deliver the data is to create classes that insert the data over some dao functionality.

Because creating indices though JPA is not possible we need sql scripts to insert them. Because of that I tend to provide the data though native sql scripts.

What functionality do you use to provide the data? Is there a "best" way to do this?
Paul Sturrock
Bartender

Joined: Apr 14, 2004
Posts: 10336

We use PowerDesigner to generate database specific scripts from a logical model which works quite well, though PowerDesigner is not cheap. But it does mean you can offset some of the work testing scripts on individual platforms.


JavaRanch FAQ HowToAskQuestionsOnJavaRanch
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Database initialization and patches
 
Similar Threads
Applying patch in java web application
Prepared Stmt or Stored Procedure ?
OOP considered harmful (was: C. Date on UML book)
Sitemesh or XSLT for layout
SQL scripts for data migration