Not sure - may be it was already suggested or there is an easy way of doing this, but:
it would be very nice if we could automate generating (and running) scripts by command line call. Let's say I as a developer need to deploy something to production from testing. Our DBA always ask for backup plan - in other words, set of scripts easy allowing them to restore previous state (I assume we are talking mostly about procedures, packages, triggers, views etc. - not changing of tables structures, that are sometimes not easy to rollback). Suppose we have the ability to call PLSQL developer by command line with arguments of connection and filename with selected objects list. In this case all I have to do is to send our DBA this file and a batch file with two commands - first connects to production and creates backup script to easy rollback all the changes, second connects to testing and builds new script for building all new objects. Of course, passwords are provided by DBA, not me. If there is an additional flag for such a command line saying "run the script after creation", we can actually have completely automated procedure of deploying changes to whatever number of environments with automatically created rollback scripts. Just my 2 cents...
it would be very nice if we could automate generating (and running) scripts by command line call. Let's say I as a developer need to deploy something to production from testing. Our DBA always ask for backup plan - in other words, set of scripts easy allowing them to restore previous state (I assume we are talking mostly about procedures, packages, triggers, views etc. - not changing of tables structures, that are sometimes not easy to rollback). Suppose we have the ability to call PLSQL developer by command line with arguments of connection and filename with selected objects list. In this case all I have to do is to send our DBA this file and a batch file with two commands - first connects to production and creates backup script to easy rollback all the changes, second connects to testing and builds new script for building all new objects. Of course, passwords are provided by DBA, not me. If there is an additional flag for such a command line saying "run the script after creation", we can actually have completely automated procedure of deploying changes to whatever number of environments with automatically created rollback scripts. Just my 2 cents...
