1. Clone your PROD instance into a DEV/TEST instance, 2. Create the script, apply it to the non-PROD instance 3. Test 4. Deployp?
-Dennis "Murray Collingwood" <[EMAIL PROTECTED]> 10/24/2005 10:41 PM Please respond to "Struts Users Mailing List" <user@struts.apache.org> To Struts Users Mailing List <user@struts.apache.org> cc Subject [slightly OT] Prince of Struts questions his database maintenance strategy Hi folks This is for those of us not using Hibernate or iBatis....those still using JDBC or DBCP. You've spent 2 months (a blink in the eye of eternity really) creating your killer Struts app. It launched without any problems (you know it's a fairy tale now) and you were hailed by many fellow staff as the Prince of Struts. A few weeks have passed and the hallo has lost some of it's shine. You realise you need to make a structure change to your database. Do you: a) make the changes manually using some database maintenance tool? b) write the necessary SQL into a JSP file to be executed when you upload the new site? c) some other magical tool that performs this maintenance for you? d) tell everybody the app is perfect and the change shouldn't be made? Currently I'm using (b) above, however I'm concerned about making a mistake and accidentally running the wrong JSP file by accident, potentially screwing up my data. PS I'm not really the prince of struts or anything near it...it really is a fairy tale but I hope you had a smile while reading it. Kind regards mc FOCUS Computing Mob: 0415 24 26 24 [EMAIL PROTECTED] http://www.focus-computing.com.au -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.361 / Virus Database: 267.12.5/147 - Release Date: 24/10/2005 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
