...and god bless them for it. It's much easier that trying to manipulate
than the long column on dba_triggers, and finding what line is the line
that errored in a trigger can be a PITA.
Brian P. MacLean
Oracle DBA, OCP8i
> 'why is view and trigger text stored in LONGs'
Just a wild guess, but I would bet that in previous versions it had to
do with the fact that the objects were compiled at each execution, and
storing them as longs as opposed to friendly text somehow cut down on
that time. Or maybe that's how ever
I believe that the reason was to avoid the use of LONGs...
...wise choice, too...
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Wednesday, April 10, 2002 8:38 AM
> Dave,
>
> I was always curious about that too. The only guess I came up with
Not quite the good reason, since triggers and views are stored in LONGs and you can
get this type of message too...
Remember that procedures were introduced with Oracle 6, and there were no CLOBs then.
It was either a LONG (already used to store view text) or lines of varchars, which I
think we
Dave,
I was always curious about that too. The only guess I came up with was
wither to help with debugging when compiling, or maybe when a procedure
fails during execution to supply you with what line number is was at when
the error occurred.
Gives you a clue about how things work.
Tom Mercada
AFAIK, it has always been like that, how else would Oracle report "error at
Line 15 Col 26" ...
Raj
__
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't refle
