After going through the struggle of learning how to get things setup, I'm capturing some notes and troubleshooting at my blog, ConfessionsOfAnAgileCoach.blogspot.com but that's disatisfying as I think using my fresh eyes, I could update the 4 Step Program in a way that helps new users get going. It only needs a few tweaks to avoid waisting a lot of time. (Getting UTL_files working in XE is one example, and it's required to get most of the utplsql libs to compile. Another example is simply a better way to spell betwnstr so people don't waist time trying to simply run the example.)
A non tweak would be to document a suggested TDD workflow--maybe too big a topic and maybe too tools dependent. I'm working on a good workflow now. Another non-tweak is a "how to" do unit testing in Oracle using FlywayDB for versioning and migration. Although that would fit on my blog, DB migration automation is an important strategy that the world needs to start getting up to speed so we stop doing some dumb things over and over again. We need to get our fellow software pros to stop thinking of automating DB migration (and unit testing) as an "advanced outlier" and instead make it the deriguer. Just as as all coversations about doing procs in a DB should include automated unit tests, changes to DB should be versoined and managed with automated migration tools.
How do you feel about this and will you work with me?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After going through the struggle of learning how to get things setup, I'm capturing some notes and troubleshooting at my blog, ConfessionsOfAnAgileCoach.blogspot.com but that's disatisfying as I think using my fresh eyes, I could update the 4 Step Program in a way that helps new users get going. It only needs a few tweaks to avoid waisting a lot of time. (Getting UTL_files working in XE is one example, and it's required to get most of the utplsql libs to compile. Another example is simply a better way to spell betwnstr so people don't waist time trying to simply run the example.)
A non tweak would be to document a suggested TDD workflow--maybe too big a topic and maybe too tools dependent. I'm working on a good workflow now. Another non-tweak is a "how to" do unit testing in Oracle using FlywayDB for versioning and migration. Although that would fit on my blog, DB migration automation is an important strategy that the world needs to start getting up to speed so we stop doing some dumb things over and over again. We need to get our fellow software pros to stop thinking of automating DB migration (and unit testing) as an "advanced outlier" and instead make it the deriguer. Just as as all coversations about doing procs in a DB should include automated unit tests, changes to DB should be versoined and managed with automated migration tools.
How do you feel about this and will you work with me?
Hi Lance, that sounds great :)
On a personal level, I like the sound of FlywayDB, but I'm inclilned to agree that that might be a bit too specific for utPLSQL's documentation.
Have you had a look at the documentation source code in SVN? Let me know if it's not obvious or if you've got any questions.
Thanks for the pointer on using svn. I'll be doing more work with utPlSQL so I'll keep
that in mimd as I go through the docs again.