Database Reference
In-Depth Information
Figure 13-11.
APEX Search Application results
The problem with the results in
Figure 13-11
is that they contain results for all text
that contains
TICKETS
. This includes labels, HTML, and so on. Although this may not
seem like a problem, consider searching for the
EMP
table. You results might contain
things such as t
emp
late,
emp
loyee,
emp
no, and more. Because you only want referen-
ces to the table with respect to SQL queries and PL/SQL blocks, you might want to ex-
clude all occurrences of your search where its previous or next character is alphanu-
meric.
Regular expressions, which are supported by the APEX Search Application tool,
can be used to accomplish this. The search criteria must be prefixed with
regexp:
in
order to use regular expressions.
Figure 13-12
shows Search Application when a regu-
lar expression is used to filter out occurrences of
emp
where its previous or next char-
acter is alphanumeric.
Figure 13-12.
APEX search using a regular expression
Monitoring Your APEX Application
APEX can log each page access and login attempt. Logging is an excellent feature to
enable because it allows you to monitor your application and provides a way to help re-
duce errors and improve performance. This section shows you how to enable logging,
some uses for the activity log, and how to view all login attempts.
Enabling Logging
By default, logging is enabled when you create an application. To verify that logging is
enabled for your application, go to Shared Components, and click the Edit Application
Properties link in the Application region at the right. In the Properties section is a Log-
ging option, as shown in
Figure 13-13
. Ensure that it says Yes, and click the Apply
Changes button.
