Sorry if this comes through twice, it seems oracle-L doesn't like web 2.0
content, embedded images
Do what you're doing, just look at the compiler log vs the script output panel
Click on the error messages there, we do the maths for you on the line number
stuff
Pic here => https://pbs.twimg.com/media/D2BoXA0XcAI_pHm.png
From: Paul Houghton <Paul.Houghton@xxxxxxxxxxxxx>
Sent: Tuesday, March 19, 2019 7:01 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: SQL Developer line numbers
I don't get to do much development, but I am writing a fairly simple package
and thought I would try using SQL Developer. When I get errors having run it,
the line number reported is the line in the package body, as you would expect.
However I have the package definition, some synonyms, etc. above the package
body in the file, so I have to mentally add 152 to the line number to get the
line number in the file.
Also, if there is a compile error, SQL Developer takes me to the line number in
the file rather than the line number in the package body when I click on it.
Is there a configuration option to change this behaviour to something more
useful? Or some functionality I could use to easily take me to the line number
(e.g. in vim I would go to the line above the create package body, then type in
"234j", where 234 is the line number reported, to get to the problem.)
I realise a possible solution would be to create one file per object. What do
you do?
Thanks
PaulH
