BenoƮt Mandelbrot passed away a couple of days ago, but the news wasn't reported until late saturday.
I remember spending countless hours drawing the Mandelbrot set on a HP workstation some 24 years ago.
Farewell Dr. Mandelbrot!
Welcome to Flavio Casetta's official Oracle database application development related blog.
Sunday, October 17, 2010
Thursday, October 14, 2010
Where-used feature for Apex LOVs - the missing bit
Always check out the original article at http://www.oraclequirks.com for latest comments, fixes and updates.
When working on large Apex projects, it's easy to create components that shortly after must be discarded because the customer changed his mind on a certain feature or we found a better solution for a certain problem.
So, it may happen that shared components like list of values, in short LOVs, clutter the repository and you don't remember if a particular one is still used or not.
Oracle Application Express provides you with a where-used feature in the form of a list on the right hand side of the page containing the LOV definition (see the picture below).

The downside to this approach is in that you must open each and every LOV definition and see if this list is empty or not.
If the LOVs are just a few is not a big deal, but with dozens of them, it is certainly a waste of time.
Fortunately the apex dictionary views come to the rescue.
It doesn't take too long to come up with a couple of queries returning a list of all used and unused lists of values and this query is fairly simpler than the query i wrote for tracking build options time ago.
See more articles about Oracle Application Express or download tools and utilities.
When working on large Apex projects, it's easy to create components that shortly after must be discarded because the customer changed his mind on a certain feature or we found a better solution for a certain problem.
So, it may happen that shared components like list of values, in short LOVs, clutter the repository and you don't remember if a particular one is still used or not.
Oracle Application Express provides you with a where-used feature in the form of a list on the right hand side of the page containing the LOV definition (see the picture below).

The downside to this approach is in that you must open each and every LOV definition and see if this list is empty or not.
If the LOVs are just a few is not a big deal, but with dozens of them, it is certainly a waste of time.
Fortunately the apex dictionary views come to the rescue.
It doesn't take too long to come up with a couple of queries returning a list of all used and unused lists of values and this query is fairly simpler than the query i wrote for tracking build options time ago.
-- LOVs where used by app, page and component typeI hope i caught all possible components, i found that LOV column names in the dictionary come in four distinct flavors out of five total possibilities! (unless i missed some...)
select app_id, named_lov, page_id, component_type, component_name
from (
select APPLICATION_ID as app_id,
LOV_NAMED_LOV as named_lov,
PAGE_ID,
'PAGE ITEM' as component_type,
ITEM_NAME as component_name
from apex_application_page_items
union all
select APPLICATION_ID as app_id,
NAMED_LIST_OF_VALUES as named_lov,
PAGE_ID,
'REPORT COLUMN' as component_type,
COLUMN_ALIAS as component_name
from APEX_APPLICATION_PAGE_RPT_COLS
-- comment out the following query if running on Apex 3.2
union all
select APPLICATION_ID as app_id,
NAMED_LOV,
PAGE_ID,
'INTERACTIVE REPORT COLUMN' as component_type,
COLUMN_ALIAS as component_name
from APEX_APPLICATION_PAGE_IR_COL
--
) a
where app_id = :APP_ID
and a.named_lov in (select LIST_OF_VALUES_NAME
from APEX_APPLICATION_LOVS b
where b.APPLICATION_ID = a.app_id)
order by app_id, named_lov, page_id;
-- unused LOVs
select APPLICATION_ID as app_id,
LIST_OF_VALUES_NAME as named_lov
from APEX_APPLICATION_LOVS
where APPLICATION_ID = :APP_ID
minus
select app_id, named_lov
from (
select APPLICATION_ID as app_id,
LOV_NAMED_LOV as named_lov
from apex_application_page_items
union
select APPLICATION_ID as app_id,
NAMED_LIST_OF_VALUES as named_lov
from APEX_APPLICATION_PAGE_RPT_COLS
-- comment out the following query if running on Apex 3.2
union
select APPLICATION_ID as app_id,
NAMED_LOV
from APEX_APPLICATION_PAGE_IR_COL
--
) a
where app_id = :APP_ID
and a.named_lov in (select LIST_OF_VALUES_NAME
from APEX_APPLICATION_LOVS b
where b.APPLICATION_ID = a.app_id);
See more articles about Oracle Application Express or download tools and utilities.
Wednesday, October 13, 2010
SQLDeveloper 3.0EA1 is here
Always check out the original article at http://www.oraclequirks.com for latest comments, fixes and updates.
Shortly after the release of SQLDeveloper Data Modeler, the awaited SQLDeveloper 3.0 early adopter version has been released today.
I'm very pleased to see that SQLDeveloper now includes a full fledged node for DBMS_SCHEDULER, something I've been longing for ever since and it really looks very cool!
I strongly recommend to read Kris' blog posting as he provided some nifty demo videos of the new features.
Shortly after the release of SQLDeveloper Data Modeler, the awaited SQLDeveloper 3.0 early adopter version has been released today.
I'm very pleased to see that SQLDeveloper now includes a full fledged node for DBMS_SCHEDULER, something I've been longing for ever since and it really looks very cool!
I strongly recommend to read Kris' blog posting as he provided some nifty demo videos of the new features.
How to copy an Apex region and its items within the same page
Always check out the original article at http://www.oraclequirks.com for latest comments, fixes and updates.
Ever needed to duplicate a region along with its items within the same page?
If you attempt to copy a region and its items to the same page, you will get the following message in Apex 4.0:
This restriction can be easily circumvented by first copying the region to a different page and then, from there, back to the original page. So, you may want to create an unused page in Apex just for doing this sort of operations. Clearly this is a convenient method if the region contains a lot of items, if a region contains only one or two items you might be better off copying the region without items and then duplicating the items manually.
I know it seems fairly trivial, but when you get a show stopper message like that above, the first reaction is probably to give up when there is actually a fairly simple workaround in the Apex arsenal that does the trick in a matter of seconds.
See more articles about Oracle Application Express or download tools and utilities.
Ever needed to duplicate a region along with its items within the same page?
If you attempt to copy a region and its items to the same page, you will get the following message in Apex 4.0:

I know it seems fairly trivial, but when you get a show stopper message like that above, the first reaction is probably to give up when there is actually a fairly simple workaround in the Apex arsenal that does the trick in a matter of seconds.
See more articles about Oracle Application Express or download tools and utilities.
Tuesday, October 12, 2010
Now i know why they call it a "primary need"
Recently i heard that in a few countries of the world, the access to internet has been declared a primary need.
I believe Finland and Iceland are among the countries and i have no doubt that they are taking the web very seriously.
But as it always happens with us Italians, the so-called primary need could be interpreted in a different way altogether, as we shall see.
So, what is a primary need in the first place?
Water, bread, peace or....?
The right answer can be easily with the help of the instant search of Google, that is the capability of the search engine to supply fresh results while typing.
Yesterday for some reason i was looking for images on www.google.it, so i began typing the letter B and the type ahead feature quickly suggested me some terms (the most frequently sought coming first i guess):
Belen Rodriguez
Belen Rodriguez senza mutande (translation: Belen Rodriguez without pants)
and presumably other less interesting results.
I called a friend of mine and asked to repeat the search using a diffent OS and a different browser and he got the same answer.
Then i typed D and the most sought terms were
Donne senza niente addosso (tr: women without cloths)
Donne senza reggiseno e mutande (tr: women without bra and without pants)
Donne spogliate completamente (tr: completely naked women)
etc.
For C the most sought term was "Cristiano Ronaldo", for L "Lady Gaga" and "Larissa Riquelme", for M "Megan Fox", for N "Nina Senicar", for P "Pokemon" immediately followed by "porcherie sessuali" (tr. wild sex), for S "Shakira", for T "ti amo" (tr. I love you) followed by "tattoo".
Eventually we found some real poets!
For what I've seen these results are fairly unique in the google realm, i tried with google.es, google.fr, google.com.mx, google.is and google.de, but none returned something alike (except "Britney Spears" in Spain), so either the search terms are really different or Google is serving me some generic terms basing on my geographic location.
Well, even without any scientific pretension, it must mean something.
I believe Finland and Iceland are among the countries and i have no doubt that they are taking the web very seriously.
But as it always happens with us Italians, the so-called primary need could be interpreted in a different way altogether, as we shall see.
So, what is a primary need in the first place?
Water, bread, peace or....?
The right answer can be easily with the help of the instant search of Google, that is the capability of the search engine to supply fresh results while typing.
Yesterday for some reason i was looking for images on www.google.it, so i began typing the letter B and the type ahead feature quickly suggested me some terms (the most frequently sought coming first i guess):
Belen Rodriguez
Belen Rodriguez senza mutande (translation: Belen Rodriguez without pants)
and presumably other less interesting results.
I called a friend of mine and asked to repeat the search using a diffent OS and a different browser and he got the same answer.
Then i typed D and the most sought terms were
Donne senza niente addosso (tr: women without cloths)
Donne senza reggiseno e mutande (tr: women without bra and without pants)
Donne spogliate completamente (tr: completely naked women)
etc.
For C the most sought term was "Cristiano Ronaldo", for L "Lady Gaga" and "Larissa Riquelme", for M "Megan Fox", for N "Nina Senicar", for P "Pokemon" immediately followed by "porcherie sessuali" (tr. wild sex), for S "Shakira", for T "ti amo" (tr. I love you) followed by "tattoo".
Eventually we found some real poets!
For what I've seen these results are fairly unique in the google realm, i tried with google.es, google.fr, google.com.mx, google.is and google.de, but none returned something alike (except "Britney Spears" in Spain), so either the search terms are really different or Google is serving me some generic terms basing on my geographic location.
Well, even without any scientific pretension, it must mean something.
Monday, October 11, 2010
SQLDeveloper Data Modeler anyone?
Always check out the original article at http://www.oraclequirks.com for latest comments, fixes and updates.
Breaking news about SQL Developer Data Modeler FREE Early Adopter version.
Breaking news about SQL Developer Data Modeler FREE Early Adopter version.
Thursday, October 07, 2010
What's new in Apex 4.0 dictionary?
Always check out the original article at http://www.oraclequirks.com for latest comments, fixes and updates.
A year and a half ago I published a short article about apex 3.2 dictionary's new entries in comparison with version 3.1.
It's now the time to re-run those queries against Apex 4.0.1 and Apex 3.2.1.
Given the wealth of changes introduced with Apex 4.0.1, the total list of new columns exceeds 1200 rows, so i will only publish here the columns added to views that were existing in Apex 3.2, but of course you can run these queries on your own to see the full results.
The queries can be executed inside Apex SQL Workshop provided you haven't already dropped schema APEX_030200.
See more articles about Oracle Application Express or download tools and utilities.
A year and a half ago I published a short article about apex 3.2 dictionary's new entries in comparison with version 3.1.
It's now the time to re-run those queries against Apex 4.0.1 and Apex 3.2.1.
Given the wealth of changes introduced with Apex 4.0.1, the total list of new columns exceeds 1200 rows, so i will only publish here the columns added to views that were existing in Apex 3.2, but of course you can run these queries on your own to see the full results.
The queries can be executed inside Apex SQL Workshop provided you haven't already dropped schema APEX_030200.
select view_name as new_view_name
from all_views
where owner = 'APEX_040000'
and view_name like 'APEX%'
minus
select view_name as new_view_name
from all_views
where owner = 'APEX_030200'
and view_name like 'APEX%';
NEW_VIEW_NAME
------------------------------
APEX_APPLICATION_PAGE_DA
APEX_APPLICATION_PAGE_DA_ACTS
APEX_APPLICATION_PAGE_FLASH5
APEX_APPLICATION_PAGE_FLASH5_S
APEX_APPLICATION_PAGE_IR_COMP
APEX_APPLICATION_PAGE_IR_GRPBY
APEX_APPLICATION_PAGE_IR_SUB
APEX_APPLICATION_PAGE_TREES
APEX_APPLICATION_TRANS_MAP
APEX_APPL_PLUGINS
APEX_APPL_PLUGIN_ATTRIBUTES
APEX_APPL_PLUGIN_ATTR_VALUES
APEX_APPL_PLUGIN_EVENTS
APEX_APPL_PLUGIN_FILES
APEX_DEBUG_MESSAGES
APEX_TEAM_BUGS
APEX_TEAM_FEATURES
APEX_TEAM_FEEDBACK
APEX_TEAM_FEEDBACK_FOLLOWUP
APEX_TEAM_MILESTONES
APEX_TEAM_TODOS
APEX_UI_DEFAULTS_ATTR_DICT
APEX_UI_DEFAULTS_GROUPS
APEX_WORKSPACE_LOG_ARCHIVE
APEX_WS_APPLICATIONS
APEX_WS_APP_PAGES
APEX_WS_DATA_GRID
APEX_WS_DATA_GRID_COL
28 rows selected
-- new columns (full list)
select b.table_name, b.column_name as new_column_name, b.comments
from
(select table_name, column_name
from all_tab_columns
where owner = 'APEX_040000'
and table_name like 'APEX%'
minus
select table_name, column_name
from all_tab_columns
where owner = 'APEX_030200'
and table_name like 'APEX%') a, all_col_comments b
where b.owner = 'APEX_040000'
and b.table_name = a.table_name
and b.column_name = a.column_name;
--------------------------------------------------
1221 rows selected (results omitted)
-- new columns added to existing views
select b.table_name, b.column_name, b.comments
from
(select table_name, column_name
from all_tab_columns
where owner = 'APEX_040000'
and table_name like 'APEX%'
minus
select table_name, column_name
from all_tab_columns
where owner = 'APEX_030200'
and table_name like 'APEX%') a, all_col_comments b
where b.owner = 'APEX_040000'
and b.table_name = a.table_name
and b.column_name = a.column_name
and b.table_name in (
select view_name
from all_views
where owner = 'APEX_030200'
and view_name like 'APEX%');
TABLE_NAME | COLUMN_NAME | COMMENTS |
---|---|---|
APEX_APPLICATIONS | AUTO_TIME_ZONE | Automatic time zone. Will derive the client time zone from the browser and set the database session timezone automatically at the beginning of each APEX session |
APEX_APPLICATIONS | DEFAULT_ERROR_DISPLAY_LOCATION | The default error display location identifies where validation error message will display. Messages can be displayed on an error page, or inline with the existing page. Inline validations are displayed in the "notification" area (defined as part of the page template), and/or within the item label. |
APEX_APPLICATIONS | PUBLISH | Display this application in a list of available applications |
APEX_APPLICATIONS | TIMESTAMP_FORMAT | Application default timestamp format. Will set NLS_TIMESTAMP_FORMAT prior to showing or posting a page |
APEX_APPLICATIONS | TIMESTAMP_TZ_FORMAT | Application default timestamp time zone format. Will set NLS_TIMESTAMP_TZ_FORMAT prior to showing or posting a page |
APEX_APPLICATION_LIST_ENTRIES | PRIMARY_APPLICATION_ID | |
APEX_APPLICATION_LIST_ENTRIES | TRANSLATED_APP_LANGUAGE | |
APEX_APPLICATION_LOV_ENTRIES | PRIMARY_APPLICATION_ID | |
APEX_APPLICATION_LOV_ENTRIES | TRANSLATED_APP_LANGUAGE | |
APEX_APPLICATION_PAGES | CREATED_BY | APEX developer who created the page. |
APEX_APPLICATION_PAGES | CREATED_ON | Date the page was created. |
APEX_APPLICATION_PAGES | JAVASCRIPT_CODE | Identifies Javascript code that replaces the #JAVASCRIPT_CODE# substitution string in the Page Template |
APEX_APPLICATION_PAGES | JAVASCRIPT_CODE_ONLOAD | Identifies JavaScript code which is executed after page load |
APEX_APPLICATION_PAGE_BUTTONS | EXECUTE_VALIDATIONS | Identifies if built-in validations and page validations should be executed when the page is submitted. |
APEX_APPLICATION_PAGE_IR | BASE_TABLE_OR_VIEW | Table or View used as the base for this interactive report region. |
APEX_APPLICATION_PAGE_IR | DETAIL_VIEW_AFTER_ROWS | Identifies the HTML to be displayed after report rows |
APEX_APPLICATION_PAGE_IR | DETAIL_VIEW_BEFORE_ROWS | Identifies the HTML to be displayed before report rows |
APEX_APPLICATION_PAGE_IR | DETAIL_VIEW_ENABLED_YN | Identifies that detail view is enabled and selectable from the interactive report |
APEX_APPLICATION_PAGE_IR | DETAIL_VIEW_FOR_EACH_ROW | Identifies the HTML to be displayed for each report row |
APEX_APPLICATION_PAGE_IR | ICON_VIEW_ALT_TEXT | Identifies the HTML ALT text for the image. |
APEX_APPLICATION_PAGE_IR | ICON_VIEW_COLUMNS_PER_ROW | Identifies the number of icons to be displayed per row |
APEX_APPLICATION_PAGE_IR | ICON_VIEW_ENABLED_YN | Identifies that an icon view is enabled and selectable from the interactive report |
APEX_APPLICATION_PAGE_IR | ICON_VIEW_IMG_ATTR_TEXT | Identifies the image attributes used for the HTML IMG tag. |
APEX_APPLICATION_PAGE_IR | ICON_VIEW_IMG_SRC_COLUMN | Identifies the report column that returns the image source |
APEX_APPLICATION_PAGE_IR | ICON_VIEW_LABEL_COLUMN | Identifies the report column that returns the image label |
APEX_APPLICATION_PAGE_IR | ICON_VIEW_LINK_COLUMN | Identifies the report column that returns the link target of the icon |
APEX_APPLICATION_PAGE_IR | ICON_VIEW_TITLE_TEXT | Identifies the HTML TITLE tag for the image. |
APEX_APPLICATION_PAGE_IR | NUMBER_OF_ALT_DEFAULT_REPORTS | Number of developer-defined alternative default reports for this report region |
APEX_APPLICATION_PAGE_IR | NUMBER_OF_PRIVATE_REPORTS | Number of user-defined private reports for this report region |
APEX_APPLICATION_PAGE_IR | NUMBER_OF_PUBLIC_REPORTS | Number of user-defined public shared reports for this report region |
APEX_APPLICATION_PAGE_IR | REGION_NAME | Name of the interactive report region |
APEX_APPLICATION_PAGE_IR | SAVE_PUBLIC_AUTH_SCHEME | This authorization scheme must evaluate to TRUE in order for Public option to display in Save Report dialog |
APEX_APPLICATION_PAGE_IR | SAVE_PUBLIC_AUTH_SCHEME_ID | Foreign Key |
APEX_APPLICATION_PAGE_IR | SHOW_GROUP_BY | Determines whether to show the Group By option in the Actions Menu |
APEX_APPLICATION_PAGE_IR | SHOW_NOTIFY | Determines whether to show the Notify option in the Actions Menu |
APEX_APPLICATION_PAGE_IR | SHOW_REPORTS_SELECT_LIST | Determines whether saved reports are displayed as select list in the Search Bar. |
APEX_APPLICATION_PAGE_IR | SHOW_ROWS_PER_PAGE | Determines whether to show the Rows Per Page option in the Actions Menu |
APEX_APPLICATION_PAGE_IR | SHOW_SAVE_PUBLIC | Determines whether to show the Public option in the Save Report dialog |
APEX_APPLICATION_PAGE_IR_COL | ALLOW_GROUP_BY | Determines whether to allow group by for this column. |
APEX_APPLICATION_PAGE_IR_COL | ALLOW_HIDE | Determines whether to allow hiding this column. |
APEX_APPLICATION_PAGE_IR_COL | ALLOW_HIGHLIGHTING | Determines whether to allow highlighting for this column. |
APEX_APPLICATION_PAGE_IR_COL | COLUMN_EXPR | Attribute for internal use only |
APEX_APPLICATION_PAGE_IR_COL | COMPONENT_COMMENT | Developer Comment |
APEX_APPLICATION_PAGE_IR_COL | NAMED_LOV | Identifies the Shared List of Values to be used to display and filter this report column |
APEX_APPLICATION_PAGE_IR_COL | REGION_ID | ID of the interactive report region |
APEX_APPLICATION_PAGE_IR_COL | TZ_DEPENDENT | Column is time zone dependent |
APEX_APPLICATION_PAGE_IR_COND | CONDITION_ALLOW_DELETE | Identifies whether this condition can be deleted |
APEX_APPLICATION_PAGE_IR_COND | CONDITION_EXPR_TYPE | If expression is date/time, expression type is Value |
APEX_APPLICATION_PAGE_IR_COND | TIME_ZONE | Time zone of user's database session when condition was saved |
APEX_APPLICATION_PAGE_IR_RPT | COUNT_DISTNT_COL_ON_BREAK | Identifies which columns to aggregate with a count distinct |
APEX_APPLICATION_PAGE_IR_RPT | REPORT_ALIAS | An alternate alphanumeric report identifier to use in report link |
APEX_APPLICATION_PAGE_IR_RPT | REPORT_LINK_EXAMPLE | An example to link to specific saved reports |
APEX_APPLICATION_PAGE_ITEMS | AJAX_ITEMS_TO_SUBMIT | Identifies the page items which should be submitted when an AJAX call is performed for the page item. |
APEX_APPLICATION_PAGE_ITEMS | AJAX_OPTIMIZE_REFRESH | Yes or No, identifies if the AJAX call should be optimized. |
APEX_APPLICATION_PAGE_ITEMS | ATTRIBUTE_01 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_ITEMS | ATTRIBUTE_02 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_ITEMS | ATTRIBUTE_03 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_ITEMS | ATTRIBUTE_04 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_ITEMS | ATTRIBUTE_05 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_ITEMS | ATTRIBUTE_06 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_ITEMS | ATTRIBUTE_07 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_ITEMS | ATTRIBUTE_08 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_ITEMS | ATTRIBUTE_09 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_ITEMS | ATTRIBUTE_10 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_ITEMS | DISPLAY_AS_CODE | Internal code of DISPLAY_AS |
APEX_APPLICATION_PAGE_ITEMS | ESCAPE_ON_HTTP_OUTPUT | If Yes values will be escaped when they are written to the HTTP output. |
APEX_APPLICATION_PAGE_ITEMS | IS_REQUIRED | If set to Yes, APEX will automatically perform a not null validation during page submit. |
APEX_APPLICATION_PAGE_ITEMS | LOV_CASCADE_PARENT_ITEMS | Identifies the cascading LOV parent item(s) for the item. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_LABEL_01 | The label is the the text the end user of the application will see for the quick pick. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_LABEL_02 | The label is the the text the end user of the application will see for the quick pick. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_LABEL_03 | The label is the the text the end user of the application will see for the quick pick. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_LABEL_04 | The label is the the text the end user of the application will see for the quick pick. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_LABEL_05 | The label is the the text the end user of the application will see for the quick pick. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_LABEL_06 | The label is the the text the end user of the application will see for the quick pick. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_LABEL_07 | The label is the the text the end user of the application will see for the quick pick. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_LABEL_08 | The label is the the text the end user of the application will see for the quick pick. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_LABEL_09 | The label is the the text the end user of the application will see for the quick pick. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_LABEL_10 | The label is the the text the end user of the application will see for the quick pick. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_LINK_ATTR | Link attribute which is added to each quick pick link. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_VALUE_01 | The value defines the value which is used when the quick pick is clicked. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_VALUE_02 | The value defines the value which is used when the quick pick is clicked. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_VALUE_03 | The value defines the value which is used when the quick pick is clicked. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_VALUE_04 | The value defines the value which is used when the quick pick is clicked. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_VALUE_05 | The value defines the value which is used when the quick pick is clicked. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_VALUE_06 | The value defines the value which is used when the quick pick is clicked. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_VALUE_07 | The value defines the value which is used when the quick pick is clicked. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_VALUE_08 | The value defines the value which is used when the quick pick is clicked. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_VALUE_09 | The value defines the value which is used when the quick pick is clicked. |
APEX_APPLICATION_PAGE_ITEMS | QUICK_PICK_VALUE_10 | The value defines the value which is used when the quick pick is clicked. |
APEX_APPLICATION_PAGE_ITEMS | SHOW_QUICK_PICKS | If set to Yes, the entered quick picks will be displayed below the page item. |
APEX_APPLICATION_PAGE_ITEMS | STANDARD_VALIDATIONS | Identifies where APEX will perform the built-in standard validations for the item type. |
APEX_APPLICATION_PAGE_PROC | ATTRIBUTE_01 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_PROC | ATTRIBUTE_02 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_PROC | ATTRIBUTE_03 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_PROC | ATTRIBUTE_04 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_PROC | ATTRIBUTE_05 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_PROC | ATTRIBUTE_06 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_PROC | ATTRIBUTE_07 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_PROC | ATTRIBUTE_08 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_PROC | ATTRIBUTE_09 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_PROC | ATTRIBUTE_10 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_PROC | CONDITION_TYPE_CODE | Internal code of CONDITION_TYPE |
APEX_APPLICATION_PAGE_PROC | PROCESS_POINT_CODE | Internal code of PROCESS_POINT |
APEX_APPLICATION_PAGE_PROC | PROCESS_TYPE_CODE | Internal code of PROCESS_TYPE |
APEX_APPLICATION_PAGE_REGIONS | ATTRIBUTE_01 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_REGIONS | ATTRIBUTE_02 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_REGIONS | ATTRIBUTE_03 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_REGIONS | ATTRIBUTE_04 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_REGIONS | ATTRIBUTE_05 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_REGIONS | ATTRIBUTE_06 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_REGIONS | ATTRIBUTE_07 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_REGIONS | ATTRIBUTE_08 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_REGIONS | ATTRIBUTE_09 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_REGIONS | ATTRIBUTE_10 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_REGIONS | DISPLAY_REGION_SELECTOR | |
APEX_APPLICATION_PAGE_REGIONS | LIST_ID | Associated list, if region is of type list. Can be joined to APEX_APPLICATION_LISTS. |
APEX_APPLICATION_PAGE_REGIONS | PARENT_REGION_ID | Identifies the region id of the parent region |
APEX_APPLICATION_PAGE_REGIONS | PARENT_REGION_NAME | Identifies the parent region |
APEX_APPLICATION_PAGE_REGIONS | REST_ENABLED | Identifies whether the region can be accessed via a RESTful call |
APEX_APPLICATION_PAGE_REGIONS | SOURCE_TYPE_CODE | Internal code of SOURCE_TYPE |
APEX_APPLICATION_PAGE_RPT_COLS | ATTRIBUTE_01 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_RPT_COLS | ATTRIBUTE_02 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_RPT_COLS | ATTRIBUTE_03 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_RPT_COLS | ATTRIBUTE_04 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_RPT_COLS | ATTRIBUTE_05 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_RPT_COLS | ATTRIBUTE_06 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_RPT_COLS | ATTRIBUTE_07 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_RPT_COLS | ATTRIBUTE_08 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_RPT_COLS | ATTRIBUTE_09 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_RPT_COLS | ATTRIBUTE_10 | Dynamic attribute to store additional data |
APEX_APPLICATION_PAGE_RPT_COLS | DISPLAY_AS_CODE | Internal code of DISPLAY_AS |
APEX_APPLICATION_PAGE_RPT_COLS | IS_REQUIRED | If set to Yes, APEX will automatically perform a not null validation during page submit. |
APEX_APPLICATION_PAGE_RPT_COLS | STANDARD_VALIDATIONS | Identifies where APEX will perform the built-in standard validations for the report column type. |
APEX_APPLICATION_PAGE_VAL | ALWAYS_EXECUTE | If set to Yes this flag will overwrites the "Execute Validations" flag for buttons and always execute the validation. |
APEX_APPLICATION_PAGE_VAL | ASSOCIATED_COLUMN | If applicable, select the column associated with this validation error message. |
APEX_APPLICATION_PAGE_VAL | TABULAR_FORM_REGION_ID | Identifies the region ID of the tabular form region for column validations |
APEX_APPLICATION_PAGE_VAL | WHEN_BUTTON_PRESSED_ID | Foreign key to button |
APEX_APPLICATION_PROCESSES | ATTRIBUTE_01 | Dynamic attribute to store additional data |
APEX_APPLICATION_PROCESSES | ATTRIBUTE_02 | Dynamic attribute to store additional data |
APEX_APPLICATION_PROCESSES | ATTRIBUTE_03 | Dynamic attribute to store additional data |
APEX_APPLICATION_PROCESSES | ATTRIBUTE_04 | Dynamic attribute to store additional data |
APEX_APPLICATION_PROCESSES | ATTRIBUTE_05 | Dynamic attribute to store additional data |
APEX_APPLICATION_PROCESSES | ATTRIBUTE_06 | Dynamic attribute to store additional data |
APEX_APPLICATION_PROCESSES | ATTRIBUTE_07 | Dynamic attribute to store additional data |
APEX_APPLICATION_PROCESSES | ATTRIBUTE_08 | Dynamic attribute to store additional data |
APEX_APPLICATION_PROCESSES | ATTRIBUTE_09 | Dynamic attribute to store additional data |
APEX_APPLICATION_PROCESSES | ATTRIBUTE_10 | Dynamic attribute to store additional data |
APEX_APPLICATION_PROCESSES | PROCESS_TYPE_CODE | Internal code of PROCESS_TYPE |
APEX_APPLICATION_TEMP_LIST | FIRST_LIST_TEMPLATE_CURRENT | First list template for current entry template. Defaults to list template current. |
APEX_APPLICATION_TEMP_LIST | FIRST_LIST_TEMPLATE_NONCURRENT | First list template for non current entry template. Defaults to list template non current. |
APEX_APPLICATION_TEMP_LIST | FITEM_TEMPLATE_NONCURR_W_CHILD | First item template for non current entry with child |
APEX_APPLICATION_TEMP_LIST | F_ITEM_TEMPLATE_CURR_W_CHILD | First item template for current entry with child |
APEX_APPLICATION_TEMP_REGION | SUB_REGION_HEADER_ENTRY_TEMPL | HTML that defined the appearance of a single sub region header entry |
APEX_APPLICATION_TEMP_REGION | SUB_REGION_HEADER_TEMPLATE | HTML that defined the appearance of a sub region header |
APEX_APPLICATION_TEMP_REGION | SUB_REGION_TEMPLATE | HTML that defined the appearance of a sub region |
APEX_APPLICATION_THEMES | DEFAULT_IRR_TEMPLATE | Identifies the default template when creating new components of a corresponding type |
APEX_APPLICATION_WEB_SERVICES | SOAP_VERSION | Identifies the SOAP version of the service, 1.1 or 1.2 |
APEX_DEVELOPER_ACTIVITY_LOG | OBJECT_NAME | The name of the affected component (stored at time of action) |
APEX_DEVELOPER_AUDIT_LOG | OBJECT_NAME | The name of the affected component (stored at time of action) |
APEX_UI_DEFAULTS_COLUMNS | FORM_ATTRIBUTE_01 | When creating a form against this table or view, this dynamic attribute stores additional information for item type specified in display_as_form. |
APEX_UI_DEFAULTS_COLUMNS | FORM_ATTRIBUTE_02 | When creating a form against this table or view, this dynamic attribute stores additional information for item type specified in display_as_form. |
APEX_UI_DEFAULTS_COLUMNS | FORM_ATTRIBUTE_03 | When creating a form against this table or view, this dynamic attribute stores additional information for item type specified in display_as_form. |
APEX_UI_DEFAULTS_COLUMNS | FORM_ATTRIBUTE_04 | When creating a form against this table or view, this dynamic attribute stores additional information for item type specified in display_as_form. |
APEX_UI_DEFAULTS_COLUMNS | FORM_ATTRIBUTE_05 | When creating a form against this table or view, this dynamic attribute stores additional information for item type specified in display_as_form. |
APEX_UI_DEFAULTS_COLUMNS | FORM_ATTRIBUTE_06 | When creating a form against this table or view, this dynamic attribute stores additional information for item type specified in display_as_form. |
APEX_UI_DEFAULTS_COLUMNS | FORM_ATTRIBUTE_07 | When creating a form against this table or view, this dynamic attribute stores additional information for item type specified in display_as_form. |
APEX_UI_DEFAULTS_COLUMNS | FORM_ATTRIBUTE_08 | When creating a form against this table or view, this dynamic attribute stores additional information for item type specified in display_as_form. |
APEX_UI_DEFAULTS_COLUMNS | FORM_ATTRIBUTE_09 | When creating a form against this table or view, this dynamic attribute stores additional information for item type specified in display_as_form. |
APEX_UI_DEFAULTS_COLUMNS | FORM_ATTRIBUTE_10 | When creating a form against this table or view, this dynamic attribute stores additional information for item type specified in display_as_form. |
APEX_UI_DEFAULTS_COLUMNS | GROUP_NAME | The group associated with this column. Will be used for creating regions in forms and groups in interactive reports. |
APEX_WORKSPACES | ALLOW_APP_BUILDING_YN | Controls availability of identified component |
APEX_WORKSPACES | ALLOW_SQL_WORKSHOP_YN | Controls availability of identified component |
APEX_WORKSPACES | ALLOW_TEAM_DEVELOPMENT_YN | Controls availability of identified component |
APEX_WORKSPACES | ALLOW_TO_BE_PURGED_YN | Controls availability of identified component |
APEX_WORKSPACES | ALLOW_WEBSHEET_DEV_YN | Controls availability of identified component |
APEX_WORKSPACES | SOURCE_IDENTIFIER | Identifies the workspace when data is synchronized to other systems. |
APEX_WORKSPACE_ACTIVITY_LOG | CONTENT_LENGTH | The size of the web page served. |
APEX_WORKSPACE_ACTIVITY_LOG | INTERACTIVE_REPORT_ID | Identifies the Interactive Report ID foreign key to the APEX_APPLICATION_PAGE_IR view |
APEX_WORKSPACE_ACTIVITY_LOG | IR_SAVED_REPORT_ID | Identifies the Saved Interactive Report ID foreign key to the APEX_APPLICATION_PAGE_IR_RPT view |
APEX_WORKSPACE_ACTIVITY_LOG | IR_SEARCH | The search text entered from Interactive Report search bar |
APEX_WORKSPACE_ACTIVITY_LOG | WS_APPLICATION_ID | Websheet application primary key, unique over all workspaces |
APEX_WORKSPACE_ACTIVITY_LOG | WS_DATAGRID_ID | ID of the Websheet application Data Grid |
APEX_WORKSPACE_ACTIVITY_LOG | WS_PAGE_ID | ID of the Websheet application page |
See more articles about Oracle Application Express or download tools and utilities.
Friday, October 01, 2010
Ig Nobel 2010 winners finally revealed
As I owe to the prestigious Annals of Improbable Research the inspiration for the title of this blog, i thought that we could end this week with a good laugh by reading the list of this year's winners of the IG-Nobel awards.
I am particularly happy for my fellow countryman who won the Management Prize
by "demonstrating mathematically that organisations would become more efficient if they promoted people at random", a theory that I find not only revolutionary, but also absolutely true.
I am particularly happy for my fellow countryman who won the Management Prize
by "demonstrating mathematically that organisations would become more efficient if they promoted people at random", a theory that I find not only revolutionary, but also absolutely true.
Labels:
off topic
Subscribe to:
Posts (Atom)
yes you can!
Two great ways to help us out with a minimal effort.
Click on the Google Plus +1 button above or...
We appreciate your support!