Re: Very long "WHERE" list.

From: Andy Hassall <andy_at_andyh.co.uk>
Date: Sat, 10 Jul 2004 16:52:19 +0100
Message-ID: <jr30f0d6bis56vgblavqh6b3l8cc8apa2n@4ax.com>

On Sat, 10 Jul 2004 16:39:19 +0100, Andy Hassall <andy_at_andyh.co.uk> wrote:

>>BEGIN
>> dbms_output.put_line(NULL);
>>END;
>>/
>
> No, it's not. The NULL here doesn't have a type, and so it'll raise a
>compile-time exception as there's several overloads of put_line and not enough
>information to select one.

 Looks like this has changed in 10g. In 9i it raises an exception:

Connected to:
Oracle9i Enterprise Edition Release 9.2.0.5.0 - Production With the Partitioning option
JServer Release 9.2.0.5.0 - Production

SQL> begin
  2 dbms_output.put_line(null);
  3 end;
  4 /
   dbms_output.put_line(null);
   *
ERROR at line 2:

ORA-06550: line 2, column 4:
PLS-00307: too many declarations of 'PUT_LINE' match this call
ORA-06550: line 2, column 4:

PL/SQL: Statement ignored

 10g accepts it:

Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production With the Partitioning and Data Mining options

SQL> begin
  2 dbms_output.put_line(null);
  3 end;
  4 /

PL/SQL procedure successfully completed.

 A side-effect of the PL/SQL parser improvements in 10g?

--
Andy Hassall <andy_at_andyh.co.uk> / Space: disk usage analysis tool
http://www.andyh.co.uk         / http://www.andyhsoftware.co.uk/space

Received on Sat Jul 10 2004 - 10:52:19 CDT