As Published In
Oracle Magazine
March/April 2012

UP FRONT: 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.

 

Documentation Dearth

Security for Everyone” by Frank Nimphius (January/February 2012) offers the most comprehensive example I have seen on how to secure applications in Oracle Application Development Framework (Oracle ADF). But as much as I enjoyed looking through it, it lacked the procedures for deployment into Oracle WebLogic Server, configuration in Oracle WebLogic Server, and procedures for Oracle Access Manager to protect the Oracle ADF application. It is really tough to get the full picture if one needs to go digging for it in a ton of docs to get a sample working.
Madhu Iyengar

Frank Nimphius replies: I agree that a single document covering Oracle ADF security and related technologies (such as Oracle Access Manager) is needed to make it easier for developers to develop and deploy secure applications. However, such a document, if done right, would probably have a page count between 100 and 150 pages. But I will surely get back to security in a future article, and deployment is a good security topic.

In regards to complete Oracle ADF and related security documentation, there currently is a related discussion on the Oracle ADF Enterprise Methodology Group forum aiming at gathering requirements for such a write-up. The URL for your reference is bit.ly/zmYCTq. This group is free of charge and open to everyone, so you may want to contribute to the effort with your ideas and the requirements you see. For the time being, I’ll copy your requirements to the thread so they are listed there. Thanks for reading the Oracle ADF column.

E-Mail the Editors


Send your opinions about what you read in Oracle Magazine, and suggestions for possible technical articles, to opubedit_us@oracle.com. Or click the Write the Editors link on our Website, oracle.com/oraclemagazine. You can also follow our @oraclemagazine Twitter feed or join us on Facebook. Letters may be edited for length and clarity and may be published in any medium. We consider any communications we receive publishable.

Speak English

I received an offer to renew my subscription to your magazine, but it will be difficult to do so unless you decide to put out an edition in the English language. I can read the Technology section without any trouble, and I can even read columns that talk about more-esoteric technologies that I have not studied.

But the front of the magazine is filled with some sort of unintelligible MIS [management information systems] buzzword gibberish, and although English is my native language and I have been programming in Oracle Database for more than 20 years, I find it almost impossible to read. I appreciate learning about various hot new concepts, some of which may actually be useful, but it would help if you would define terms instead of assuming that I have read about them in the other 20 MIS magazines that I don’t subscribe to.
Michael Zvi Krumbein 

Lost in Translation

In “Working with Strings” by Steven Feuerstein (September/October 2011), I stumbled upon an error. Where Feuerstein writes about replacing characters in a string, it says: “Notice that when you are replacing a single character, the effect of REPLACE and INSTR is the same.” I’m sure that he wanted to say “. . . the effect of REPLACE and TRANSLATE is the same.”
Silvio Marghitola

Steven Feuerstein replies: Thanks, Silvio, for catching this. The online article has been corrected.

Sevens and Nines

I am reading the “Modeling and Accessing Relational Data” SQL 101 column by Melanie Caffrey (November/December 2011). On page 73 Caffrey writes, “Note that the SALARY column’s datatype is defined as NUMBER(9, 2). The first number in the parentheses (9 in this example) is referred to as the precision, and the second number (2 in this example) is known as the scale. This precision and this scale mean that the SALARY column can have a maximum of nine digits before the decimal point and two digits after it.”

It’s very refreshing to read a SQL 101 column like this (because I learned this 15 years ago in graduate school). But from what I have learned about the Oracle NUMBER datatype, (9, 2) means that the total number of digits that can be stored is 9, with a maximum of 7 digits before the decimal point and a maximum of 2 digits after it.
Ben Gong

The editors reply: Thanks for pointing out the error. The online article has been corrected.

 

 

Send us your comments