FROM OUR READERS
From Our Readers
Your corrections, your opinions, and your requests: Here's your forum for telling us what's right and wrong in each issue of Oracle Magazine, and for letting us know what you want to read.
Thanks and More
In the January/February 2004 issue of Oracle Magazine, the article I liked most was "Expect More Service."
I'd like to see more articles related to Java and Oracle, especially articles containing examples.
Nirav Patel
nirav@myrealbox.com
Cuts to Cutting
Please tell me what happened to the "Cutting Edge" section in the January/February 2004 issue of Oracle Magazine?
I hope you don't eliminate it. I think it's very good!
Felipe Alzate
felipe.alzate@ingeneo.biz
We liked the "Cutting Edge" section and all of the miscellaneous cutting-edge technology presented there, but we have eliminated the section so that we can cover more of Oracle's own cutting-edge technology.
Listing to the Right
I just read (another) excellent online article from Oracle Magazine, March/ April 2004: "Cleaning Up PL/SQL Practices," by Steven Feuerstein. Unfortunately, Listing 5 is not available online, even though the article expressly states that it is.
Would you please rectify this situation and make it available?
Sunette van Zyl
svanzyl@deecal.com
Thanks for pointing out this error. Listing 5 is now available with the article at
otn.oracle.com/oramag/oracle/04-mar/ o24tech_plsql.html.
All Oracle Magazine readers are encouraged to report any errors in Oracle Magazine print or online content to
opubedit_us@oracle.com.
A Downstream Request
I would love to see a good how-to article on how to implement Oracle Streams in Oracle9i and Oracle 10g.
Roger Eisentrager
Roger.Eisentrager@MeridianIQ.com
Closing Time
I read the article "Oracle 10g Adds More to FORALL" in the January/February 2004 issue of Oracle Magazine, and I am very surprised about the coding examples. Regarding Listing 1, I am astonished that (1) the cursor is never closed and (2) the FOR .. IN .. LOOP is not used.
Cedric
cedric@dbsolution-be.com
Wow! Your letter demonstrates the power and importance of code review. You are absolutely right! I neglected to include a CLOSE statement for my cursor in Listing 1. Rather than terminating my program with
36 END LOOP;
37* END give_raises_in_department;
I should have ended it as follows:
36 END LOOP;
37 CLOSE emp_cur;
38* END give_raises_in_department;
It is always best to clean up after yourself, although you should also know that this cursor will be closed by Oracle, because it was declared locally in this block.
Your second point is also well taken. Because I am fetching each and every row from the cursor, I should use a cursor FOR loop. Then I do not need to explicitly open and close the cursor. You should not, however, use a cursor FOR loop if you are exiting conditionally from the loop.
The code for using a cursor FOR loop is in the revised Listing 1 with the online version of this article, at otn.oracle.com/oramag/oracle/04-jan/o14tech_plsql.html.
Steven Feuerstein
steven@stevenfeuerstein.com
Making Errors Public
|
Send Mail to the Editor
Send your opinions about what you read in Oracle Magazine, and suggestions for possible technical articles, to opubedit_us@oracle.com.
Or click on the Write the Editors link on our Web site.
Letters may be edited for length and clarity and
may be published in any medium. We consider any communications we receive publishable.
|
I really enjoyed the article "Keeping Information Private with VPD," by Arup Nanda, in the March/April 2004 issue of Oracle Magazine. I quickly put together a solution based on the samples that I can use for some of my real-world projects. I did spot one bug in Listing 4, though:
statement_types => 'SELECT',
I believe that the comma at the end of this line shouldn't be there. Otherwise, it was a fantastic article.
Scott Sargent
sargent@ssmagic.com
The comma should not be there; it was mistakenly added during our editorial process. Listing 4 has been updated with the online version of the article, at otn.oracle.com/oramag/oracle/04-mar/o24tech_security.html.
|