ITEM | NAME |
---|---|
Apple | John |
Banana | John |
Banana | John |
Apple | John |
Apple | John |
Pear | John |
Pear | John |
Peach | John |
Peach | John |
Peach | John |
We can turn off the option by running "set markup html off",
ITEM | NAME |
---|---|
Apple | John |
Banana | John |
Banana | John |
Apple | John |
Apple | John |
Pear | John |
Pear | John |
Peach | John |
Peach | John |
Peach | John |
We can turn off the option by running "set markup html off",
ITEM |
Apple |
Banana |
Banana |
Apple |
Apple |
Pear |
Pear |
Peach |
Peach |
Peach |
Orange |
Orange |
Orange |
Orange |
Orange |
ITEM | NUM |
Orange | 5 |
Apple | 3 |
Peach | 3 |
Banana | 2 |
Pear | 2 |
ITEM | NUM | RANK |
Orange | 5 | 1 |
Apple | 3 | 2 |
Peach | 3 | 3 |
Banana | 2 | 4 |
Pear | 2 | 5 |
ITEM | NUM | RANK |
Orange | 5 | 1 |
Apple | 3 | 2 |
ITEM | NUM | RANK |
Orange | 5 | 1 |
Apple | 3 | 2 |
Peach | 3 | 2 |
Banana | 2 | 3 |
Pear | 2 | 3 |
ITEM | NUM | RANK |
Orange | 5 | 1 |
Apple | 3 | 2 |
Peach | 3 | 2 |
For those who know how to write SQL scripts, Oracle Apex is a great tool to present the analytic result online. There is no need to learn another web authoring language. Almost everything is done using SQL, reports, charts, Checkboxes, radioes, select lists. Once I spent a few days and built an internal employee fraud monitoring tool for a bank.
I have found that building report online using Apex is far more efficient than using Excel spreadsheet.
The following screenshot is from one of the reports that I built using Oracle Apex.
A project manager from a bank just told me that the model developed by me has resulted in 60% reduction in fraud loss. He said "everyone was surprised at how effective it was." It was a model that I developed two years ago for a top 15 bank.(Of course, I was not surprised at all since the model was tested on holdout data sets and showed similar performance).
The model was built and deployed on Oracle databases. The main reason for the success of the model was that I spent huge amount of effort building model variables that captures the fraud patterns. Luckily, I used Oracle analytic functions to build those variables easily. (Please see my posts "How to build predictive models that win competitions" and "Recency, Frequency, Monetary (RFM) Analysis: Part 1"
Another important advantage of using an uniform platform, i.e., Oracle databases, is that the deployment is easy. I simply deployed the model as a set of SQL query. See my posts "Build Predictive Models Using PL/SQL" and "Logistic Regression Model Implemented in SQL"
select to_char(dt_tm, 'YYYY') yy, to_char(DT_TM, 'MM') mm, to_char(DT_TM,'DD') dd, to_char(DT_TM, 'HH24') hh, to_char(DT_TM, 'MI') mi, to_char(DT_TM,'SS') ss, min(price) mi_p, avg(price) a_p, max(price) mx_p from MV_VIX3 group by to_char(dt_tm, 'YYYY'),to_char(DT_TM, 'MM'),to_char(DT_TM,'DD'),to_char(DT_TM, 'HH24'),to_char(DT_TM, 'MI'), to_char(DT_TM,'SS')
SQL> select query from user_mviews where mview_name='MV_ALL_FOR_SUM';It is very helpful as we can always find out the logic that is used to created the view. This is one of the advantage of using views over tables.
We can query Oracle user_source to get the source code about functions, procedures, triggers, etc. User_source contains 4 columns, i.e., name, type, line and text.
On my schema, the following query shows that there are 55 lines of source code for functions, 50 lines of source code for procedures, etc.
SQL> select type, count(*) from user_source group by type order by type;The following query shows the definition of a function z_cap. Thus, user_source is a very handy way to retrieve the source code.
SQL> select line, text from user_source where name='Z_CAP';