Skip to main content

PL/SQL Brain Teaser: compile procedure with two declarations with same name?

I posted my second PL/SQL brain teaser on Twitter today @sfonplsql:

I can compile a procedure successfully even tho it contains two declarations with the same name for the identifier. Can you?

 But Twitter is probably not the best way to do this, since it is not easy to capture every nuance in a tweet.

 For example, Jonathan Whitehead asked: "Complier directives?"

Which leads me to "tweak" the brain teaser to fully elaborate as follows:

 The Brain Teaser

 I can compile a procedure successfully even though it contains two declarations with the same name for the identifier. And after compilation, if I run DBMS_PREPROCESSOR.print_post_processed_source to display the actual source code that was compiled into the database, it will show BOTH of those declarations.

 OK....now, clever PL/SQL developers, can you post an example of code that will solve this teaser?

Comments

  1. Oren Nakdimon (@DBoriented)April 9, 2015 at 10:13 AM

    Just don't reference them...

    CREATE OR REPLACE PROCEDURE p AS
    x NUMBER;
    x NUMBER;
    y NUMBER;
    BEGIN
    y := 5;
    END p;
    /

    ReplyDelete
  2. Steven FeuersteinApril 9, 2015 at 10:19 AM

    Nice work, Oren. Yes, that is the solution! It turns out that the PL/SQL compiler will not complain about two declarations with the same name - as long as you do not reference them in your code.

    ReplyDelete
  3. Atul GuptaApril 10, 2015 at 4:39 AM

    CREATE OR REPLACE PROCEDURE p AS
    x NUMBER := 8;
    x NUMBER := 9;
    y NUMBER;
    BEGIN
    DEClARE
    x NUMBER;
    BEGIN
    x := 6;
    END;
    END p;
    /

    ReplyDelete
  4. Steven FeuersteinApril 10, 2015 at 8:20 AM

    A pleasantly confusing variation on Oren's work. Nice, Atul.

    ReplyDelete
  5. Atul GuptaApril 10, 2015 at 8:45 AM

    Thanks Steven....

    How about


    CREATE OR REPLACE PROCEDURE p AS
    x NUMBER := -88888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888889999999999999999999999999999999999999988;
    x NUMBER := 9;
    y NUMBER;
    BEGIN
    DEClARE
    x NUMBER;
    BEGIN
    x := 6;
    END;
    END p;
    /

    It gives error numeric overflow or underflow.......

    looks like Oracle Checks initial assignment

    ReplyDelete
  6. Steven FeuersteinApril 10, 2015 at 8:48 AM

    Yes, an assignment of a default value would certainly count as a usage of that variable.

    ReplyDelete
  7. Atul GuptaApril 10, 2015 at 8:53 AM

    Steven One more

    CREATE OR REPLACE PROCEDURE p AS
    x NUMBER := -9999999999999988;
    x NUMBER := abs(-9) * 0;
    y NUMBER;
    BEGIN
    DEClARE
    x NUMBER;
    BEGIN
    x := 6;
    END;
    END p;
    /

    It complies OK.

    ReplyDelete
  8. Steven FeuersteinApril 10, 2015 at 8:56 AM

    Well you know what means? I was wrong! :-)

    And that's what happens when you state things about code without actually verifying them. Thanks, Atul!

    ReplyDelete
  9. iudithApril 10, 2015 at 10:01 AM

    Hello Steven, All,
    I think that it is a compiler bug that it does allow the duplicate declaration in the first place.
    Steven, unrelated to this issue, I would thank you in advance if you can look into
    a feedback that I just posted on the plsqlchallenge site ... I know that you don't have access to e-mail ...
    Thanks a lot & 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

Table Functions, Part 1: Introduction and Exploration

Please do feel encouraged to read this and my other posts on table functions, but you will learn much more about table functions by taking my Get Started with PL/SQL Table Functions class at the Oracle Dev Gym. Videos, tutorials and quizzes - then print a certificate when you are done! Table functions - functions that can be called in the FROM clause of a query from inside the TABLE operator - are fascinating and incredibly helpful constructs. So I've decided to write a series of blog posts on them: how to build them, how to use them, issues you might run into. Of course, I am not the first to do so. I encourage to check out the  documentation , as well as excellent posts from Adrian Billington (search for "table functions") and Tim Hall . Adrian and Tim mostly focus on pipelined table functions, a specialized variant of table functions designed to improve performance and reduce PGA consumption. I will take a look at pipelined table functions in the latter part...
31 comments
Read more