I must be missing something.
Who installs maven on their production servers? Why would you have to do
that? you ask... The problem is that any secure production hosting
environment doesn't allow admin DB access from build or developer machines
(that would be insane). So to populate a new production deployment DB, it
appears as if you have to either:
1. Install maven on the production DB server and then run the appropriate
target (not really an option).
2. Create a production profile in your pom. Create the database, export the
database as a dump file,
import it into your prod DB server, deploy the app.
In 1.9.4, for first-time production deployments you could export the DDL as
a text file (SQL commands).
This doesn't really deal with db changes as the code and schema changes over
time. This was fairly simple in 1.9.4 though not well-suited to automated
testing. I read somewhere that 2.0 makes it easier to test schema changes
(start from 0, apply upgrade x, apply upgrade y). But this still doesn't
really deal with production vs dev.
It's certainly a great idea to reduce developer cycle time, but unless all
you're doing is prototyping, you're going to deploy to production eventually
and then you'll need to upgrade that database as you add entities. Has
anyone come up with a fairly portable system for upgrading?
Also, is there an equivalent in 2.0 that produces the SQL commands file like
occurred in 1.9.4?
On 11/28/07, Michael Horwitz <mike.horw...@gmail.com> wrote:
>
> If you are running the tests against a production database surely you
> should run the data population piece as well?
>
--
View this message in context:
http://www.nabble.com/Preopopulating-a-production-database-tp13871810s2369p22316779.html
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net
For additional commands, e-mail: users-h...@appfuse.dev.java.net
