Lifecycle Management - Expert Oracle Application Express - page 396

It is immediately clear where each column originates from since each column name is unique
within all tables of the data model.
Using the APEX wizards to generate a page on this view will result in the following items being
created automatically (assuming the new page number is 8): P8 BOOK ID , P8 BOOK RES ID ,
P8 BOOK LOC ID , P8 RES TITLE , P8 REST TITLE , P8 LOC CITY , P8 CON TITLE , P8 CON ID , P8 USR LAST NAME ,
P8 BOOK BOOKED FROM , P8 BOOK BOOKED UNTIL , P8 BOOK UPDATED BY , P8 BOOK UPDATED ON .
This time it is immediately obvious that P8 BOOK ID refers to a row in the table FM BOOKINGS . Also,
P8 BOOK UPDATED BY and P8 BOOK UPDATED ON refer to auditing information within the same table.
Using the same column name consistently throughout the data model has another advantage. If you
change the contents of a specific column, you can easily find all occurrences of this column in your data
model and in your APEX application.

Naming Conventions for the File System
To organize the file system, first we start with a few general rules. They were established for a single
purpose: we didn't want to think about how to name and structure things over and over again, but
wanted to follow simple rules once agreed upon. This is just one way to do it, but the gain in
transparency and productivity is significant.

• Folder names in singular form: Most of the time the folders in your file system will

be in a mix of singular form and plural form. We have agreed to write all folder
names in singular form. This is neither good nor bad, just consistent and easy to
follow.

• Organization by source type, then by module: In the source tree we always start

with the source type (sql, java, apex, etc.). Within each type we will organize the
code by their respective modules, e.g., hierarchically organized Java packages. For
the SQL source part (which also includes PLSQL) we organize the files by their
respective schema. This makes it easier for the development tools to work with
this layout.

The different elements of the suggested file system layout are described in more detail in Table 9-3.

Table 9-3. File System Layout Structure

Directory Description

src This is the top level of the source tree.

src/apex

This folder contains all APEX related files which will be
uploaded into the workspace.

src/apex/app image In this folder we store all files (*.css, *.js, *.jpg, *.png, etc.) which

will be uploaded into the workspace (dependent on a specific
application). They will be referenced in your application using
the #APP IMAGES# <filename> syntax.