background image
<< Related Documents | Introducing Schema Objects >>
<< Related Documents | Introducing Schema Objects >>

Overview of Oracle Database and Development

Overview of Oracle Database and Development 1-1
1
Overview of Oracle Database and
Development
This chapter introduces you to application development with Oracle Database.
This chapter contains the following sections:
Roadmap
on page 1-1
Overview of Oracle Database Schemas
on page 1-2
Overview of Application Development with Oracle Database
on page 1-3
Overview of Other Development Environments
on page 1-10
Roadmap
You are an Oracle Database developer, someone who has the responsibility of creating
or maintaining the database components of an application that uses the Oracle
technology stack. The discussion in this and following sections assumes that you, or
someone else in your organization, must know how to architect multiuser applications
(two tier or multitier) and understands the advantages of using a relational database
for the data persistence tier.
As a database developer, you need to know how to implement the data model that the
application requires, how to implement the rules for data integrity, and how to
implement the specified functions for accessing and manipulating the application
data.
You know already that you can access an Oracle Database only through a client
program, and that the SQL language is that client program's interface to the Oracle
Database. You will learn how to access the Oracle Database by using two clients that
are packaged with the Oracle Database and designed for developers: SQL Developer
and SQL*Plus. Both allow you to issue the SQL statements you need in order to create
and test your application's database component without doing any client
programming. Programming such clients is outside the scope of this discussion.
To briefly review widely accepted best practices in software engineering, you must
define APIs that model business functions, and hide the implementation. Oracle
Database supports this practice by letting you specify the APIs as PL/SQL
subprograms. The implementation is tables, indexes, constraints, triggers, and the
various SQL statements that modify and fetch table rows. By embedding these SQL
statements in PL/SQL subprograms, and by using Oracle's schema and privilege
mechanisms, you can securely hide the implementation from the client programs.
Many of Oracle's major customers follow this practice strictly: client programs are
allowed to access the database only by calling PL/SQL subprograms. Some customers