SQL Editor |
If an SQL statement that produces a result set is executed from the SQL editor, a Table editor is automatically opened. Each next result editor will be opened in the same area you may have moved the first editor in. That gives you the chance to use the editors with the same feeling that the Instant SQL view gives you with seeing both statement and result at the same time. |
|
|
Connection
Configuration |
In addition ![]() |
|
|
Miscellaneous |
Oracle (TM) drivers do not
explicitly close cursors that they
have opened when answering a request for primary key references, index
information of a table or the like. This is an error because the JDBC
api doesn't give a chance to close the cursor from outside the method. Workaround: As this is the case with index tables which cannot be automatically detected you should skip those tables in search operations (not enclose them in the selected scope). Otherwise all searches over that kind of tables lead to an exception and leave a cursor open, which will quickly let the connection run out of available cursors. |
|