Skip to main content

Best laid plans or why no new post on table functions this week

I was doing so well: 1 post in my series on table functions each week.

I planned to complete a description of the table function I used in the PL/SQL Challenge rankings report, which I began here.

But then, well, things got in the way. Things like:

  • Write my next article for Oracle Magazine, only one week past due
  • Write five daily tips on PL/SQL via @sfonplsql
  • Produce two new quizzes for the PL/SQL Challenge.
  • Record a video for ODTUG to promote the YesSQL! Day at Kscope15
  • Record a "train the trainer" video to pass on some tips on how to give excellent (or at least highly entertaining) presentations.
  • Donate a small bucket of white cells and plasma to LifeSource.
  • Waaay too many conference call/meetings and waaaaaay too much email.
  • Finish up work on a root canal. Fun!
  • Cut down a bunch of invasive buckthorn (I so love that the sun sets so late in the day now!).
  • Help design and test some exciting new features for Oracle Learning Library
So my apologies, dear readers. Next week. Next week I am certain, I pledge, I promise, I will share you with my amazing table function, filled with a really complicated dynamic SQL query.

In the meantime, have a great weekend!

Comments

  1. iudithMay 1, 2015 at 10:34 AM

    Hello Steven,
    So great to hear that amidst the so many Oracle-related tasks, you still find
    the time for making good to others ... and, maybe, saving someone's life,
    either a human or another being ......
    Anyway, still much better to be in the position of making good to others,
    than, God forbid, fighting desperately to rescue your own life.
    Oracle is beautiful, but it can still "wait in the queue", behind other much more
    important things.
    I am sure that even the most fanatic Oracle-ists will agree with this order
    of priorities, and patiently wait for their turn :):)

    Have a great weekend & Best Regards,
    Iudith

    ReplyDelete

Post a Comment

Popular posts from this blog

Why DBMS_OUTPUT.PUT_LINE should not be in your application code

A database developer recently came across my  Bulletproof PL/SQL  presentation, which includes this slide. That first item in the list caught his attention: Never put calls to DBMS_OUTPUT.PUT_LINE in your application code. So he sent me an email asking why I would say that. Well, I suppose that is the problem with publishing slide decks. All the explanatory verbiage is missing. I suppose maybe I should do a video. :-) But in the meantime, allow me to explain. First, what does DBMS_OUTPUT.PUT_LINE do? It writes text out to a buffer, and when your current PL/SQL block terminates, the buffer is displayed on your screen. [Note: there can be more to it than that. For example, you could in your own code call DBMS_OUTPUT.GET_LINE(S) to get the contents of the buffer and do something with it, but I will keep things simple right now.] Second, if I am telling you not to use this built-in, how could text from your program be displayed on your screen? Not without a lot o...
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: Three ways to get error message/stack in PL/SQL

The PL/SQL Challenge quiz for 10 September - 16 September 2016 explored the different ways you can obtain the error message / stack in PL/SQL. Note: an error stack is a sequence of multiple error messages that can occur when an exception is propagated and re-raised through several layers of nested blocks. The three ways are: SQLERRM - The original, traditional and (oddly enough) not currently recommended function to get the current error message. Not recommended because the next two options avoid a problem which you are unlikely  to run into: the error stack will be truncated at 512 bytes, and you might lose some error information. DBMS_UTILITY.FORMAT_ERROR_STACK - Returns the error message / stack, and will not truncate your string like SQLERRM will. UTL_CALL_STACK API - Added in Oracle Database 12c, the UTL_CALL_STACK package offers a comprehensive API into the execution call stack, the error stack and the error backtrace.  Note: check out this LiveSQL script if...
5 comments
Read more