![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Tim Slattery (Slattery_T (AT) bls (DOT) gov) wrote: : I can enter stored procedures/functions and packages in SQL*Plus, : that works fine. Except when there's a syntax error someplace. Then it : tells me something like "Warning: Package Body created with : compilation errors." But it doesn't tell me WHAT the errors are! It : doesn't work that way with an anonymous PL/SQL block, that gives a : fine syntax error report. : Is there something I can set to get it to tell me what it objects to? : I scanned the list of SET options, tried autotrace and flagger, still : lost. sql> show errors If there aren't any errors then it says "No errors.", and it's cleared after each successful code creation, so it's useful to to simply call it every time. prompt creating foobar @foobar show error prompt creating bazbar @bazbar show error |
#12
| |||
| |||
|
|
Tim Slattery (Slattery_T (AT) bls (DOT) gov) wrote: : I can enter stored procedures/functions and packages in SQL*Plus, : that works fine. Except when there's a syntax error someplace. Then it : tells me something like "Warning: Package Body created with : compilation errors." But it doesn't tell me WHAT the errors are! It : doesn't work that way with an anonymous PL/SQL block, that gives a : fine syntax error report. : Is there something I can set to get it to tell me what it objects to? : I scanned the list of SET options, tried autotrace and flagger, still : lost. sql> show errors If there aren't any errors then it says "No errors.", and it's cleared after each successful code creation, so it's useful to to simply call it every time. prompt creating foobar @foobar show error prompt creating bazbar @bazbar show error |
#13
| |||
| |||
|
|
Tim Slattery (Slattery_T (AT) bls (DOT) gov) wrote: : I can enter stored procedures/functions and packages in SQL*Plus, : that works fine. Except when there's a syntax error someplace. Then it : tells me something like "Warning: Package Body created with : compilation errors." But it doesn't tell me WHAT the errors are! It : doesn't work that way with an anonymous PL/SQL block, that gives a : fine syntax error report. : Is there something I can set to get it to tell me what it objects to? : I scanned the list of SET options, tried autotrace and flagger, still : lost. sql> show errors If there aren't any errors then it says "No errors.", and it's cleared after each successful code creation, so it's useful to to simply call it every time. prompt creating foobar @foobar show error prompt creating bazbar @bazbar show error |
#14
| |||
| |||
|
|
Tim Slattery (Slattery_T (AT) bls (DOT) gov) wrote: : I can enter stored procedures/functions and packages in SQL*Plus, : that works fine. Except when there's a syntax error someplace. Then it : tells me something like "Warning: Package Body created with : compilation errors." But it doesn't tell me WHAT the errors are! It : doesn't work that way with an anonymous PL/SQL block, that gives a : fine syntax error report. : Is there something I can set to get it to tell me what it objects to? : I scanned the list of SET options, tried autotrace and flagger, still : lost. sql> show errors If there aren't any errors then it says "No errors.", and it's cleared after each successful code creation, so it's useful to to simply call it every time. prompt creating foobar @foobar show error prompt creating bazbar @bazbar show error |
#15
| |||
| |||
|
|
Tim Slattery (Slattery_T (AT) bls (DOT) gov) wrote: : I can enter stored procedures/functions and packages in SQL*Plus, : that works fine. Except when there's a syntax error someplace. Then it : tells me something like "Warning: Package Body created with : compilation errors." But it doesn't tell me WHAT the errors are! It : doesn't work that way with an anonymous PL/SQL block, that gives a : fine syntax error report. : Is there something I can set to get it to tell me what it objects to? : I scanned the list of SET options, tried autotrace and flagger, still : lost. sql> show errors If there aren't any errors then it says "No errors.", and it's cleared after each successful code creation, so it's useful to to simply call it every time. prompt creating foobar @foobar show error prompt creating bazbar @bazbar show error |
![]() |
| Thread Tools | |
| Display Modes | |
| |