Hi Kirill
Thanks for your answer.
The reason I am polluting a Java forum with database questions is because of the architecture of the application I currently work on.
It originated as Oracle Forms on an Oracle database, with a lot of business logic in database procedures and triggers.
More recently most new development has been carried out in JSP/Servlets/Struts against the common database - the original forms still being used.
The Java code base is in CVS and is built nightly using
Ant. The Java Developers mostly use Idea 5 so TeamCity seems a logical next step.
Database schema, code and static data are in CVS, the build script can be automatically generated but running it is a manual task.
Slipping into Martin Luther King mode for a moment - I Have a Dream...
...That the build of Java, Forms and Database can be treated equally. That it can be made completely automatic, with notifications of build failure and test failure for each of the code bases.
I am happy to roll as much of my own code as necessary (totally automatic DB build is the first step I would take), but since developer time is a scarce resource, the more TeamCity can do for me, or the more hooks into TeamCity functionality I can use the better.
So, are there features of TeamCity that we haven't already discussed that might help me in my quest?
Regards
Chris