Skip to main content

Object Types and Object-Oriented Development with PL/SQL: the Series

Find below the list of my blog posts in a series on working with object types (a.k.a, classes) in Oracle Database and, specifically, PL/SQL.

This series is not intended to offer an in-depth training on object-oriented development; instead, it introduces basic O-O concepts and shows how they are implemented in Oracle Database with PL/SQL.

Introduction to Object Types, Part 1
Object Types and Inheritance, Part 2
Object Types Methods, Part 3
Using Object Types in Relational Tables, Part 4
Comparison Methods for Object Types, Part 5
Dynamic Polymorphism - Why, What, How, Part 6

Each post also contains a link to a LiveSQL script, so you can try out all the code yourself.

Labels:

Comments

  1. rwienerOctober 24, 2019 at 5:35 AM

    Great serie :-)

    But I am not able to see part 3 Object type methods - error "Invalid securityToken. Error 403"

    Very thanks

    ReplyDelete
  2. StevenFeuersteinOctober 24, 2019 at 5:38 AM

    Hmmm. Sorry to hear this. I just tried the link on three different browsers and did not have any trouble. Did you try a different browser? Clear your cookies?

    ReplyDelete
    Replies
    1. Richard SmithOctober 24, 2019 at 5:51 AM

      The above link to Part 3 contains "/b/post-preview?token=" which returns the "Invalid security Token" error, but a blog search for the article title brings up the actual post successfully: https://stevenfeuersteinonplsql.blogspot.com/2019/09/object-type-methods-part-3.html

      Delete
    2. StevenFeuersteinOctober 24, 2019 at 5:59 AM

      Oy, I am such a goof! Thanks, Richard, yes, the URL I had pasted in there was my preview link. I have now fixed this to use the correct URL.

      Delete

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

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