SQL Developer line numbers
From: Paul Houghton <Paul.Houghton_at_uis.cam.ac.uk>
Date: Tue, 19 Mar 2019 11:00:34 +0000
Message-ID: <DB6PR0701MB2997F8732DF0ABE12E992561E6400_at_DB6PR0701MB2997.eurprd07.prod.outlook.com>
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.
Date: Tue, 19 Mar 2019 11:00:34 +0000
Message-ID: <DB6PR0701MB2997F8732DF0ABE12E992561E6400_at_DB6PR0701MB2997.eurprd07.prod.outlook.com>
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
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Mar 19 2019 - 12:00:34 CET