Databases Reference
In-Depth Information
Category
Convention
Description
<view name>
.sql
Examples:
fm bookings v.sql
Views
<procedure name>
.sql
Procedures
<function name>
.sql
Functions
<package name>
.pks
Package headers
The package specification and the package body
are separated; this way we get fewer compile-
time errors due to dependency issues.
<package name>
.pkb
Package bodies
The package specification and the package body
are separated; this way we get fewer compile-
time errors due to dependency issues.
<type name>
.tb
Type bodies
The type specifications and the type bodies are
separated; this way we get fewer compile-time
errors due to dependency issues.
<table name> trg
.sql
Trigger
The triggers might reference other functions or
tables but cannot be referenced themselves.
Thus we will get fewer compile-time errors when
we install the triggers at the end of the script.
Furthermore, the triggers can be automatically
extracted and copied into the patch directory.
Examples:
fm bookings trg.sql
fm countries trg.sql
<table name> data
.sql
Examples:
fm bookings data.sql
fm countries data.sql
Data
Here we store the relevant DML scripts to insert,
update, or delete data from the table.
script
<name>
.sql
Examples:
script copy bookings.sql
script install workflow.sql
Scripts
All relevant custom scripts. We try to name them
in the same way we would name a function or
procedure.
grants.sql
Grants
All grants (giving other users access to our data)
will be placed in a single file.
This way it is a lot easier to understand the
security implications of a new software version.
