Re: Forms3.0 Inserts w/in Procedure

From: Steven P. Muench <smuench_at_oracle.com>
Date: Mon, 17 Jan 1994 09:33:13 GMT
Message-ID: <SMUENCH.94Jan17013313_at_doh.oracle.com>


MIKE -- You're hitting a simple problem of name precedence. You have

        a parameter named 'code' and a column named 'code'. In a SQL
        statement in PL/SQL if there is an ambiguity between the
        name of a column and the name of a local variables, the column
        name "wins". Change your procedure parameter to 'the_code' 
        and the WHERE clause to ... CODE = the_code ... and you should
        be all set.

        What's really happening is your getting all rows from the
        TABLE table where CODE = CODE (i.e. where the value in the
        CODE column equals itself). That means you'll get all rows
        except where CODE IS NULL, which won't pass the CODE = CODE
        test.
--

Steve Muench         Email: smuench_at_oracle.com
Forms Development      CIS: 73404,676
Product Manager
Oracle Corporation
Received on Mon Jan 17 1994 - 10:33:13 CET

Original text of this message