Re: Developer/2000 PL/SQL editor limits package size???
From: Paul G Young <pgy_at_magma.ca>
Date: Thu, 01 Oct 1998 00:50:58 GMT
Message-ID: <01bdecd5$91ffede0$7005bfce_at_default>
Martin Vorbeck <vorbeck_at_val.indra.es> wrote in article <360FC12A.FC9D92CC_at_val.indra.es>...
> Hi,
>
> using Developer/2000's PL/SQL editor to edit database packages, I
> ran into the following limitation.
> When my package body grows very large, there comes a point where
> characters typed are not inserted any more.
> Deleting some characters (e.g. comments) allows me to insert as many
> characters as I have deleted. It happens for example
> with a package body reaching 59379 bytes total size.
>
> Using SQL Worksheet, on the other hand, I am able to increase the
> size of the package body without problems, using
> CREATE OR REPLACE PACKAGE BODY AS ....
>
> So, if I understand well, it seems that Developer/2000 (Version 1.5)
> limits the size because of some restriction with the
> PL/SQL editor. Now my question: is this so? Does anyone know a trick to
> work around this limitation?
>
> Of course I could always use a SQL script with CREATE OR REPLACE as
> I go along editing my package, thus editing directly the script, but
> this gets quite tedious, especially as far as compilation error
> detection goes. I haven't found a more convenient way to directly
> display compilation errors, other than through Developer/2000's PL/SQL
> editor...
>
> Thanks for any help or insights on this issue,
>
> Cheers,
>
> -- Martin Vorbeck
> Valencia, Spain
>
>
Received on Thu Oct 01 1998 - 02:50:58 CEST
Date: Thu, 01 Oct 1998 00:50:58 GMT
Message-ID: <01bdecd5$91ffede0$7005bfce_at_default>
I find this very interesting. You see, I've traditionally written my PL/SQL freehand in a text editor (my favourite is 'vi' :) ). There is no limit on the file size ... until I try to run it.
PL/SQL has a documented RDBMS internal limit in size - Oracle has acknowledged it and cannot fix it until (at least version 8.1). It gives a very strange error once it gets into the engine. We found the limit was about 2000 lines of PL/SQL (SQL statements don't add to the count).
The workaround we needed to use was splitting up routines across packages or use PRO*C. This was am awful error to encounter and figure out. Watch out for it.
Hope this helps.
PGY
Martin Vorbeck <vorbeck_at_val.indra.es> wrote in article <360FC12A.FC9D92CC_at_val.indra.es>...
> Hi,
>
> using Developer/2000's PL/SQL editor to edit database packages, I
> ran into the following limitation.
> When my package body grows very large, there comes a point where
> characters typed are not inserted any more.
> Deleting some characters (e.g. comments) allows me to insert as many
> characters as I have deleted. It happens for example
> with a package body reaching 59379 bytes total size.
>
> Using SQL Worksheet, on the other hand, I am able to increase the
> size of the package body without problems, using
> CREATE OR REPLACE PACKAGE BODY AS ....
>
> So, if I understand well, it seems that Developer/2000 (Version 1.5)
> limits the size because of some restriction with the
> PL/SQL editor. Now my question: is this so? Does anyone know a trick to
> work around this limitation?
>
> Of course I could always use a SQL script with CREATE OR REPLACE as
> I go along editing my package, thus editing directly the script, but
> this gets quite tedious, especially as far as compilation error
> detection goes. I haven't found a more convenient way to directly
> display compilation errors, other than through Developer/2000's PL/SQL
> editor...
>
> Thanks for any help or insights on this issue,
>
> Cheers,
>
> -- Martin Vorbeck
> Valencia, Spain
>
>
Received on Thu Oct 01 1998 - 02:50:58 CEST