Mercurial > sqlpython

comparison docs/source/limitations.rst @ 247:f0f293d83337

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
begin docs
author catherine@dellzilla
date Wed, 04 Mar 2009 17:44:29 -0500
parents
children 3ce9a48aa3fc
comparison
equal deleted inserted replaced
246:b5d4a122354a 247:f0f293d83337
1 ===========
2 Limitations
3 ===========
4
5 Slow parsing
6 ------------
7
8 After each line of text in a multi-line command is entered, SQLPython pauses to determine whether
9 the command is finished yet. This pause is unnoticable at first, but gradually becomes noticable,
10 then annoying, then crippling when very long commands are entered.
11
12 This problem can be worked around by bracketing long, individual commands in REMARK BEGIN
13 and REMARK END statements. When SQLPython finds a REMARK BEGIN, it stops parsing after each
14 line and assumes that everything entered until REMARK END is a single statement.
15
16 PL/SQL
17 ------
18
19 SQLPython interprets short anonymous PL/SQL blocks correctly, as well as one-line PL/SQL
20 commands preceded with `exec`. For longer blocks, however, it gets confused about where
21 the statement begins and ends.
22
23 To parse PL/SQL safely, enclose each free-standing PL/SQL block between a REMARK BEGIN and a
24 REMARK END statement.
25
26 Unsupported commands
27 --------------------
28
29 * DBMS_OUTPUT.PUT_LINE
30