A lot of Noetix people have migrated to Noetix Workbench for the modification
of their Noetix View environment. We have not.
Anyways, I am a Vimmer and a Noetix dude (administration, support and developer) for a
6.0.1 environment and I have found that this process below to work quite well for
capturing errors with my customized xu2/xu4 scripts:
1. Type out xu2/xu4 script modifications. Usually, I have an existing xu2/xu4
file.
2. With Vim, I just place a mark at the beginning of my new DML. Marking just is a
way to reference a row in a document for easy, quick access. Typically, I use
the mark, b, which I associated with the beginning of my noteworthy selection.
3. When I am done with my modifications to my xu2/xu4 script, I use the Vim ex
command:
:'b,$s/^COMMIT;/--COMMIT;/g
Explanation:
-'b,$ is a range for the s (substitute) command.
-^ is an anchor. Anchors are used in regular expressions to identify the location. In this context, the anchor, ^, is used to indicate the beginning of a line.
-'^COMMIT' is the searched for expression.
-'--COMMIT' is the replaced texts.
I perform this substitute for all of the commits so that I can rollback the command after it is executed. section.
4. Yank the text from this modification section using this Vim ex
command:
:'b,$y*
This just means, from the mark, b, to the end of the document, $, yank
(translation place contents in register). With my Vim instance, *, refers to
the Windows clipboard. Thus, this command moves the text from my selected
area and places this in the clipboard.
5. Start-up Windows Powershell (which I have set my profile variable,
$profile, to automagically start-up SQL Plus). I issue the spool C:\temp.lst
command in SQL Plus.
6. Paste my new modification script to SQL Plus using the Noetix
System user account.
7. Issue the spool off command.
8. Undo the substitution command in step #3 using the u normal mode
command (undo). This results in the COMMIT commands being non-commented.
9. Perform a rollback in SQL Plus so that my DML does not get committed.
9. Lastly, I peruse my spool file, C:\temp.lst, for errors using the Vim
normal mode search command:
/ORA-[0-9]\+
In summary, this is a nice, efficient way to capture errors in new DML
xu2/xu4 scripts without needing to kick-off a regeneration.
of their Noetix View environment. We have not.
Anyways, I am a Vimmer and a Noetix dude (administration, support and developer) for a
6.0.1 environment and I have found that this process below to work quite well for
capturing errors with my customized xu2/xu4 scripts:
1. Type out xu2/xu4 script modifications. Usually, I have an existing xu2/xu4
file.
2. With Vim, I just place a mark at the beginning of my new DML. Marking just is a
way to reference a row in a document for easy, quick access. Typically, I use
the mark, b, which I associated with the beginning of my noteworthy selection.
3. When I am done with my modifications to my xu2/xu4 script, I use the Vim ex
command:
:'b,$s/^COMMIT;/--COMMIT;/g
Explanation:
-'b,$ is a range for the s (substitute) command.
-^ is an anchor. Anchors are used in regular expressions to identify the location. In this context, the anchor, ^, is used to indicate the beginning of a line.
-'^COMMIT' is the searched for expression.
-'--COMMIT' is the replaced texts.
I perform this substitute for all of the commits so that I can rollback the command after it is executed. section.
4. Yank the text from this modification section using this Vim ex
command:
:'b,$y*
This just means, from the mark, b, to the end of the document, $, yank
(translation place contents in register). With my Vim instance, *, refers to
the Windows clipboard. Thus, this command moves the text from my selected
area and places this in the clipboard.
5. Start-up Windows Powershell (which I have set my profile variable,
$profile, to automagically start-up SQL Plus). I issue the spool C:\temp.lst
command in SQL Plus.
6. Paste my new modification script to SQL Plus using the Noetix
System user account.
7. Issue the spool off command.
8. Undo the substitution command in step #3 using the u normal mode
command (undo). This results in the COMMIT commands being non-commented.
9. Perform a rollback in SQL Plus so that my DML does not get committed.
9. Lastly, I peruse my spool file, C:\temp.lst, for errors using the Vim
normal mode search command:
/ORA-[0-9]\+
In summary, this is a nice, efficient way to capture errors in new DML
xu2/xu4 scripts without needing to kick-off a regeneration.
No comments:
Post a Comment