Database Reference
In-Depth Information
Figure 2-13.
The SQL Commands interface
Although its core function is quite straightforward, the SQL Commands interface is
more robust than it first appears. Beyond the ability to save and retrieve SQL and PL/
SQL, it can also run explain plans on statements and allows you to view your statement
history. Therefore, if you ran a script or statement that was particularly useful, but you
forgot to save it, you still have the potential to retrieve it from the history buffer.
The SQL Commands interface also integrates with the Query Builder (described
later), allowing you to load and manipulate saved statements built in the Query Builder.
Note
By default, all SQL statements executed via the SQL Commands interface are
automatically committed. To override this setting and enter into transactional mode, un-
check the Autocommit check box in the toolbar. Once this is done, you can manually
commit and roll back your SQL statement.
There is no way to turn off Autocommit permanently, so you need to remember to do
this any time you want to enter transactional mode.
SQL Scripts Interface
The SQL Scripts interface allows you to manage and run sets of SQL commands saved
into script files. A single script can contain one or more SQL statements or PL/SQL
blocks. SQL scripts that are coded outside of APEX can be loaded into the SQL script
repository and edited or run from there. You may also create SQL scripts from scratch
using the SQL Scripts interface.
Figure 2-14
shows the main SQL Scripts interface
page.
