DbVisualizer use by default the semicolon as the statement separator. The problem when running for example a "CREATE OR REPLACE TRIGGER" block is that this include semicolons in the body of the code. To workaround this in DbVisualizer there are several options:
1) Use of the @delimiter client side command. Example:
This will re-define the statement separator to ## and at the end of the script you put @delimiter ;## to restore semicolon as separator.
2) Enclose each of the statements between the SQL block identifiers --/ and /:
CREATE OR REPLACE PROCEDURE
3) Run each of the statements separately using the SQL->Execute Buffer command.
This will not parse the buffer for the semicolon. The drawback is that you can only run one statement at a time.
I hope this helps.
Please let me know if I can be of further assistance with any questions you may have.
about 11 years ago
[This reply is migrated from our old forums. The original author name has been removed]