Wednesday, October 30, 2019

Oracle Forms Triggers



Block Processing Triggers:
Block processing triggers fire in response to events related to record management in a block.
·        When-Create-Record Perform an action whenever Oracle Forms attempts to create a new record in a block.
·        When-Clear-Block Perform an action whenever Oracle Forms flushes the current block; that is, removes all records from the block.
·        When-Database-Record Perform an action whenever Oracle Forms changes a record’s status to Insert or Update, thus indicating that the record should be processed by the next COMMIT_FORM operation.
Interface Event Triggers:
Interface event triggers fire in response to events that occur in the form interface. Some of these triggers, such as When-Button-Pressed, fire only in response to operator input or manipulation. Others, like When-Window-Activated, can fire in response to both operator input and programmatic control.
·        When-Button-Pressed Initiate an action when an operator selects a button, either with the mouse or through keyboard selection.
·        When-Checkbox-Changed Initiate an action when the operator toggles the state of a check box, either with the mouse or through keyboard selection.
·        When-Image-Activated Initiate an action whenever the operator double-clicks an image item.
·        When-Image-Pressed Initiate an action whenever an operator clicks on an image item.
·        When-Radio-Changed Initiate an action when an operator changes the current radio button selected in a radio group item.
·        When-Window-Activated Initiate an action whenever an operator or the application activates a window.
·        When-Window-Closed Initiate an action whenever an operator closes a window with the window manager’s Close command.
·        When-Window-Deactivated Initiate an action whenever a window is deactivated as a result of another window becoming the active window.
Master/Detail Triggers:
Oracle Forms generates master/detail triggers automatically when a master/detail relation is defined between blocks. The default master/detail triggers enforce coordination between records in a detail block and the master record in a master block. Unless developing custom block-coordination schemes, you do not need to define these triggers.
·        On-Check-Delete-Master Fires when Oracle Forms attempts to delete a record in a block that is a master block in a master/detail relation.
·        On-Clear-Details Fires when Oracle Forms needs to clear records in a block that is a detail block in a master/detail relation because those records no longer correspond to the current record in the master block.
·        On-Populate-Details Fires when Oracle Forms needs to fetch records into a block that is the detail block in a master/detail relation so that detail records are synchronized with the current record in the master block.
Message-Handling Triggers:
Oracle Forms automatically issues appropriate error and informational messages in response to runtime events. Message handling triggers fire in response to these default messaging events.
·        On-Error Replace a default error message with a custom error message, or to trap and recover from an error.
·        On-Message To trap and respond to a message; for example, to replace a default message issued by Oracle Forms with a custom message.
Validation Triggers:
Validation triggers fire when Oracle Forms validates data in an item or record. Oracle Forms performs validation checks during navigation that occurs in response to operator input, programmatic control, or default processing, such as a Commit operation.
·        When-Validate-Item
·        When-Validate-Record
Navigational Triggers:
Navigational triggers fire in response to navigational events. Navigational triggers can be further sub-divided into two categories: Pre- and Post- triggers, and When-New-Instance triggers. Pre- and Post- Triggers fire as Oracle Forms navigates internally through different levels of the object hierarchy. When-New-Instance-Triggers fire at the end of a navigational sequence that places the input focus on a different item.
·        Pre-Form Perform an action just before Oracle Forms navigates to the form from “outside” the form, such as at form startup.
·        Pre-Block Perform an action before Oracle Forms navigates to the block level from the form level.
·        Pre-Record Perform an action before Oracle Forms navigates to the record level from the block level.
·        Pre-Text-Item Perform an action before Oracle Forms navigates to a text item from the record level.
·        Post-Text-Item Manipulate an item when Oracle Forms leaves a text item and navigates to the record level.
·        Post-Record Manipulate a record when Oracle Forms leaves a record and navigates to the block level.
·        Post-Block Manipulate the current record when Oracle Forms leaves a block and navigates to the form level.
·        Post-Form Perform an action before Oracle Forms navigates to “outside” the form, such as when exiting the form.
·        When-New-Form-Instance Perform an action at form start-up. (Occurs after the Pre-Form trigger fires).
·        When-New-Block-Instance Perform an action immediately after the input focus moves to an item in a block other than the block that previously had input focus.
·        When-New-Record-Instance Perform an action immediately after the input focus moves to an item in a different record.
·        When-New-Item-Instance Perform an action immediately after the input focus moves to a different item.
Transactional Triggers:
Transactional triggers fire in response to a wide variety of events that occur as a form interacts with the data source.
·        On-Delete
·        On-Insert
·        On-Update
·        On-Logon
·        On-Logout
·        Post-Database-Commit
·        Post-Delete
·        Post-Insert
·        Post-Update
·        Pre-Commit
·        Pre-Delete
·        Pre-Insert
·        Pre-Update
Query-Time Triggers:
Query-time triggers fire just before and just after the operator or the application executes a query in a block.
·        Pre-Query Validate the current query criteria or provide additional query criteria programmatically, just before sending the SELECT statement to the database.
·        Post-Query Perform an action after fetching a record, such as looking up values in other tables based on a value in the current record. Fires once for each record fetched into the block.
Advertisements
REPORT THIS AD
REPORT THIS AD
Top of Form
Bottom of Form


Sunday, October 27, 2019

Oracle Courses for all levels

Oracle Official Academy Courses

sql
pl/sql
forms
reports
1-Oracle Database 10g: Introduction to SQL
Course Topics:
- Introduction
- Retrieving Data Using the SQL SELECT Statement
- Restricting and Sorting Data
- Using Single Row Functions to Customize Reports
- Reporting Aggregated Data Using the Group Functions
- Displaying Data From Multiple Tables
- Using Sub queries to Solve Queries
- Using the SET Operators
- Manipulating Data
- Using DDL Statements to Create and Manage Tables
- Creating Other Schema Objects
- Managing Objects with Data Dictionary Views
- Controlling User Access
- Manage Schema Objects
- Manipulating Large Data Sets
- Generating Reports by Grouping Related Data
- Searching Data Using Advanced Sub queries
- Hierarchical Data Retrieval

2-Oracle Database 10g: Program with PL/SQL
Course Topics:
- Introduction to PL/SQL
- Declaring PL/SQL Identifiers
- Writing Executable Statements
- Interacting with the Oracle Server
- Writing Control Structures
- Working with Composite Data Types
- Using Explicit Cursors
- Handling Exceptions
- Creating Stored Procedures
- Creating Stored Functions
- Creating Packages
- Using More Package Concepts
- Utilizing Oracle Supplied Packages in Application Development
- Dynamic SQL and Metadata
- Design Considerations for PL/SQL Code
- Managing Dependencies
- Creating Triggers
- Applications for Triggers
- Understanding and Influencing the PL/SQL Compiler

3-Oracle Forms Developer 10g: Build Internet Applications
Course Topics:
- Introducing Oracle Forms Developer and Forms Services
- Creating Forms Modules
- Working with Data Blocks and Frames
- Working with Input Items
- Working with Non Input Items
- Working with Windows and Canvases
- Producing Triggers
- Debugging Triggers
- Adding Functionality to Items
- Run-Time Messages and Alerts
- Query Triggers
- Validation
- Navigation
- Transaction Processing
- Writing Flexible Code
- Sharing Objects and Code


4-Oracle Reports Developer 10g: Build Reports
Course Topics:
- Introduction to Oracle Reports Developer
- Designing and Running Reports
- Working in Oracle Reports Developer
- Creating a Paper Report
- Enhancing a Basic Paper Report
- Managing Report Templates
- Creating a Web Report
- Enhancing Reports Using the Data Model: Queries and Groups
- Enhancing Reports Using the Data Model: Data Sources
- Enhancing Reports Using the Data Model: Creating Columns
- Enhancing Reports Using the Paper Layout
- Controlling the Paper Layout: Common Properties
- Controlling the Paper Layout: Specific Properties
- Web Reporting
- Creating and Using Report Parameters
- Enhancing Matrix Reports
- Coding PL/SQL Triggers
- Extending Functionality Using the SRW Package


10$ per hour
            yasser.hassan@yandex.com

Thursday, October 24, 2019

Oracle Index types


Types of Indexes:
Oracle Database provides several indexing schemes, which provide complementary performance functionality. The indexes can be categorized as follows:
    B-tree indexes
    These indexes are the standard index type. They are excellent for primary key and highly-selective indexes. Used as concatenated indexes, B-tree indexes can retrieve data sorted by the indexed columns. B-tree indexes have the following subtypes:
        Index-organized tables
        An index-organized table differs from a heap-organized because the data is itself the index. See “Overview of Index-Organized Tables”.
        Reverse key indexes
        In this type of index, the bytes of the index key are reversed, for example, 103 is stored as 301. The reversal of bytes spreads out inserts into the index over many blocks. See “Reverse Key Indexes”.
        Descending indexes
        This type of index stores data on a particular column or columns in descending order. See “Ascending and Descending Indexes”.
        B-tree cluster indexes
        This type of index is used to index a table cluster key. Instead of pointing to a row, the key points to the block that contains rows related to the cluster key. See “Overview of Indexed Clusters”.
    Bitmap and bitmap join indexes
    In a bitmap index, an index entry uses a bitmap to point to multiple rows. In contrast, a B-tree index entry points to a single row. A bitmap join index is a bitmap index for the join of two or more tables. See “Bitmap Indexes”.
    Function-based indexes
    This type of index includes columns that are either transformed by a function, such as the UPPER function, or included in an expression. B-tree or bitmap indexes can be function-based. See “Function-Based Indexes”.
    Application domain indexes
    This type of index is created by a user for data in an application-specific domain. The physical index need not use a traditional index structure and can be stored either in the Oracle database as tables or externally as a file. See “Application Domain Indexes”.”