Skip to main content

Practically Perfect PL/SQL - A new video channel for PL/SQL developers!

Let this post serve as the official, groundbreaking, ground-shaking launch of (drum roll).....


This is a new Youtube/Oracle Learning Library channel that will feature my latest and greatest videos on Oracle PL/SQL and more. 

Within the P3 channel, I will set up a number and fill a number of different playlists. 


Four videos in the series are up with more to follow over the next week.

So....you might be wondering: why is this channel called "Practically Perfect PL/SQL"?

Let me count the ways:

1. Most important of all, triple alliteration: P3. Humans love alliteration and I like to give them what they want.

2. Sure, I want to talk about the features of PL/SQL, but mostly what I want to do is help developers write the best PL/SQL code they (we) can.  

We all want to be perfect, but since that is not possible, mostly what we will do is strive for perfection. We will try to be "practically" or almost perfect.

It's also a reminder to myself and everyone else writing PL/SQL and reading/watching my stuff, that I sure am not perfect. I violate my own best practices on a regular basis, I make changes in production (oh, say it isn't so, Steven!), I take short-cuts. 

3. Celebrate the practicality of programmers. We are, fundamentally, problem solvers - problem solvers working under deadlines. 

This means that when we hit an obstacle (a bug, bad requirements, changed specifications), we:
  • Never whine.
  • Never criticize another developer, especially if they are no longer on the team.
  • Never complain about users.
That's right: Never. Not us programmers, no. 

We are too practical, too pragmatic, to waste our cycles like that. We simply figure out how to work around the obstacle and get the job done.

I hope you enjoy, and maybe even learn from, the P3 videos. 

But even if you don't, please watch every single one, multiple times, so I get my view counts up really high! 

And do not hesitate to give me feedback, directly on the video page, here on this post, or through an email to steven.feuerstein@oracle.com.

Comments

  1. JAVIER DORANTES AGUILARFebruary 11, 2015 at 11:32 AM

    SQL is great I can only say this: DBASE + CLIPPER + ACCESS = SQL

    ReplyDelete
    Replies
    1. AnonymousFebruary 12, 2015 at 6:15 AM

      This comment has been removed by a blog administrator.

      Delete
  2. IngridFebruary 12, 2015 at 12:53 AM

    Not even one reference to Mary Poppins, practically perfect in every way? Maybe I did watch that movie too often.
    That said, I subscribed to this youtube channel of course! Looking forward to taking some time this weekend to watch them vids.

    ReplyDelete
  3. Steven FeuersteinFebruary 12, 2015 at 3:34 AM

    I know I watched that movie, and my wife did mention it to me as well. But clearly it didn't make a strong enough impression. :-)

    ReplyDelete
  4. AnonymousFebruary 23, 2015 at 7:46 AM

    Would you be so kind as to post the code shown in the Practically Perfect PL/SQL series?

    ReplyDelete
  5. Steven FeuersteinFebruary 24, 2015 at 1:44 AM

    Visit oracle.com/oll/plsql and download the demo.zip file. In the zip, you will find: hardcoding.sql, fullname.pks and fullname.pkb.

    ReplyDelete

Post a Comment

Popular posts from this blog

Running out of PGA memory with MULTISET ops? Watch out for DISTINCT!

A PL/SQL team inside Oracle made excellent use of nested tables and MULTISET operators in SQL, blending data in tables with procedurally-generated datasets (nested tables).  All was going well when they hit the dreaded: ORA-04030: out of process memory when trying to allocate 2032 bytes  They asked for my help.  The error occurred on this SELECT: SELECT  *    FROM header_tab trx    WHERE (generated_ntab1 SUBMULTISET OF trx.column_ntab)       AND ((trx.column_ntab MULTISET             EXCEPT DISTINCT generated_ntab2) IS EMPTY) The problem is clearly related to the use of those nested tables. Now, there was clearly sufficient PGA for the nested tables themselves. So the problem was in executing the MULTISET-related functionality. We talked for a bit about dropping the use of nested tables and instead doing everything in SQL, to avoid the PGA error. That would, however require lots of wo...
4 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch, ...
4 comments
Read more

PL/SQL 101: Save your source code to files

PL/SQL is a database programming language. This means that your source code is compiled into  and executed from within the Oracle Database. There are many fantastic consequences of this fact, many of which are explored in Bryn Llewellyn's Why Use PL/SQL? whitepaper. But this also can mean that developers see the database as the natural repository for the original source code , and this is a bad mistake to make. It's not the sort of mistake any JavaScript or Java or php developer would ever make, because that code is not compiled into the database (well, you can  compile Java into the database, but that's not where 99.99% of all Java code lives). But it's a mistake that apparently too many Oracle Database developers make. So here's the bottom line: Store each PL/SQL program unit in its own file . Use a source code control system to manage those files. Compile them into the database as needed for development and testing. In other words: you should never kee...
16 comments
Read more