PL/SQL Style Guide:
Adopt a consistent, readable format that is easy to maintain
    Capitalization & Text formatting 
        Reserved words should be in uppercase (BEGIN, DECLARE, ELSIF)
        Built-in Functions are in uppercase (SUBSTR, COUNT, TO_CHAR)
        Predefined types are in uppercase (NUMBER(7,2), BOOLEAN, DATE)
        SQL keywords are in uppercase (SELECT, INTO, UPDATE, WHERE)
        Database Objects are in lowercase (log_table, classes, students)
        Variable names are in lowercase
Adopt logical, consistent naming conventions for modules and data structures
    Variable & Parameter Declarations
        Variable names should be prefixed with one of the following 
            "gv_" for variables defined in a package specification
            "v_" for variables defined in a package body
            "lv_" for variables defined in Stored Procedures or Functions
        Variable names comprised of multiple words have an underscore between 
           each word (v_employee_id)
        Parameters should begin with "p_"
        Rather then hard coding the data type of a variable/parameter, you should 
            use the %TYPE operator when possible
    PL/SQL object naming standards (<name> describes the basic functionality contained within the PL/SQL Object)
        PL/SQL stored procedures should begin with "sp_" (i.e. "sp_<name>")
        PL/SQL functions should begin with "fx_" or "get_" (i.e. "fx_<name>" or "get_<name>")
        PL/SQL packages should end with "_pkg" (i.e. "<name>_pkg")
    Other database object naming standards
        All sequences should end with "_seq" (i.e. "<name>_seq")