Related Entries

Useful SQL*Plus headers
Dino eats frog
Oracle with Active Record
When is he free?
Gentle dive into analytic functions

« Interview with Ploners
» Language skills for programmers

Quick Links

Links I didn't want to forget later -- well, it is a Sunday morning after all.

Relevant quote from Tom Kyte, from his book Expert One-on-OneTM Oracle:

I’ve a pretty simple mantra when it comes to developing database software:
  1. You should do it in a single SQL statement if at all possible.
  2. If you cannot do it in a single SQL statement, then do it in PL/SQL.
  3. If you cannot do it in PL/SQL, try a Java stored procedure.
  4. If you cannot do it in Java, do it in a C external routine.
  5. If you cannot do it in a C external routine, you might want to seriously think about why it is you need to do it...

Words to live by. As Andy Todd commented on a previous entry, these days, I see lot of developers who pride that they do only OO programming and nothing else; and all they need a database for is to provide persistence for objects. Fine, spend time and money fighting with application servers and details of JVM or J2EE specs. I think I will still trust an Oracle server with its PL/SQL engine that has been around for a much longer time.

  1. And do you recommend Tom's book?

    Posted by: Andy Todd on January 18, 2004 01:36 PM
  2. Absolutely. It is the best book on Oracle, IMHO.

    Posted by: Babu on January 18, 2004 05:04 PM