Obviously you are right about DBI::Oracle, however, as I said in my original post, my first priority is to spend the least development effort, and that's how this was invented.

This idea does provide people with rapid development experience, but I expressly mentioned in my original post that this is for "under certain circumstances". Those certain circumstances are:

1. Not much effort to spend,
2. and the scripts are not expected to be heavily used/reused although they could be really useful when it is used.

To use sqlplus, that was also one of the solution I had, I will see whether I have Perl on that AIX, if yes, I will try this out next week. This also does not cost much effort, but it would really depends on whether Perl is there. In a corporate environment, you know, I cannot go and install whatever I want, it just does not work in that way.

POD ... Hm, as it is not a module, and mostly for my own use (I want to share the idea with everyone, but the exact code is not much useful to other people, others here may reuse my idea, but nobody would need my code as it is.), well, no execuse ;-) I think I should explain more about how it works, let me add some comments/operation sequence to the original code.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.