Mercurial > sqlpython
view docs/source/limitations.rst @ 250:aec778ef82b6
print full help on -h
author | catherine@Elli.myhome.westell.com |
---|---|
date | Thu, 12 Mar 2009 07:58:42 -0400 |
parents | f0f293d83337 |
children | 3ce9a48aa3fc |
line wrap: on
line source
=========== Limitations =========== Slow parsing ------------ After each line of text in a multi-line command is entered, SQLPython pauses to determine whether the command is finished yet. This pause is unnoticable at first, but gradually becomes noticable, then annoying, then crippling when very long commands are entered. This problem can be worked around by bracketing long, individual commands in REMARK BEGIN and REMARK END statements. When SQLPython finds a REMARK BEGIN, it stops parsing after each line and assumes that everything entered until REMARK END is a single statement. PL/SQL ------ SQLPython interprets short anonymous PL/SQL blocks correctly, as well as one-line PL/SQL commands preceded with `exec`. For longer blocks, however, it gets confused about where the statement begins and ends. To parse PL/SQL safely, enclose each free-standing PL/SQL block between a REMARK BEGIN and a REMARK END statement. Unsupported commands -------------------- * DBMS_OUTPUT.PUT_LINE