This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
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?
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.