I then load the new/changed code via TOAD to a live schema. This master changes file contains all of the changes that need to be applied to bring the live schema up to date. If the code tests out, I check the code into CVS.Īt the end, I use Cygwin bash (and a bash script I've written) to create a master changes file. In the SQL Editor menu -> Load and Execute a Script File I load the new/changed code via TOAD to a test schema. Luckily, WinCVS allows you to use an externalĭiff (Beyond Compare) which comes in very handy. I pre-configure my Textpad with SQL syntax filesĪfter editing, I Beyond Compare each edited I then use TextPad to edit the PL/SQL code. In other words I need to have a good starting baseline. I ensure that the CVS sql repository is up to date. I Beyond Compare each file version exported by TOAD These files are initially checked into CVS. I move these files (Cygwin bash script) in directories This gets me individual files for each database object. In the Database menu -> Export -> Table Scripts In the Database menu -> Export -> Source Code I use Quest Software TOAD to export all PL/SQL and table DDL code to the filesystem. Import code back using Quest Software TOAD Use a Cygwin bash script to create a master changes file.ĩ. Check code in to WinCVS / CVSNT (if needed)Ĩ. Compare versions via BeyondCompare (if needed)ħ. Check code out of WinCVS / CVSNT (if needed)Ħ. Compare versions via BeyondCompare (if needed)Ĥ. Use a Cygwin bash script to move files into the appropriate directoriesģ. Here are my PL/SQL coding core practices:Ģ. I do not trust PL/SQL software development to any of the PL/SQL IDE tools out there. I've had several crashes of Quest Software's TOAD as well as Quest Software's SQL Navigator (I've been using it since Version 3). (for more on continuous improvement/Kaizen see link text) I've tried to apply continuous improvement to SQL development and it has worked out wonderfully for me. For me PL/SQL development is a process that has evolved over time.
0 kommentar(er)
