This repository has been archived by the owner on Apr 5, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 11
PLSQL Compiling
Alexandru Tica edited this page Jun 28, 2013
·
1 revision
As an Oracle developer, is very likely to interact with a lot of PLSQL objects like: packages, types, functions, procedures etc. The code source of these database objects are usually loaded into special vorax PLSQL buffers which, unlike the SQL ones, allow to compile the corresponding PLSQL source.
The default key mapping for compiling is <Leader>c
. "C" stands, obviously, for "C"ompile. Two things happen when a PLSQL object is compiled:
- the buffer content is sent as it is to the server.
- as soon as the buffer content is executed, Vorax will check the
ALL_ERRORS
view to see if any relevant errors exist. If such errors are found, they are loaded into a Vim quickfix window, along with the error line, error column and the message itself.
Note: Pay attention that during the compilation of an PLSQL object, the substitution variables feature is disabled.
The window where the compilation errors are displayed is configurable via:
-
g:vorax_errwin_height
: the height of the error window -
g:vorax_errwin_goto_first
: whenever or not, after the error window is displayed, the cursor to be moved to the first error.