Generating Code with Oracle SQL Developer Data Modeler

Code Generation with Oracle SDDM
Rob van den Berg

Code Generation with Oracle SDDM
Presenter information
VX Company IT Services b.v.
Email rvdberg@vxcompany.com
Twitter twitter.com/rob_vd_berg
Blog rvdbergblog.wordpress.com

Code Generation with Oracle SQL Developer Data Modeler
Introduction
SDDM Features supporting Code Generation
Code Generation
Agenda

Oracle SQL Developer Data Modeler
Introduction
Introduction

Main Features - Introduction
Last version as of December 21, 2015 is 4.1.3.901
Free
Create, browse and edit relational models
Create, browse and edit multi-dimensional models
Forward and reverse engineering
Integrated source code control
Since July 1, 2009
Jeff Smith
Heli Helskyaho

– This presentation is about Application Code Generation
– Focussing on:
application code that implements Business Rules
– Code as complex as Entity Rules, Inter Entity Rules,
Change Event Rules, etc.
– In short: Code Beyond DDL
– Supporting: thick database design
(Toon Koppelaars, Bryn Llewellyn)
Main Features – Introduction – Presentation subject

Setting the stage
Features
supporting
Application
Code
Generation

Features – “Oh, pretty pictures – I can do that !!”

– ER diagramming (Barker, Bachman or IE notation)
– Engineering to and from relational models
– Supertypes and subtypes, arcs
– Compare and merge with logical model in another design
Features – Logical Models

Explore different kinds of modeling!

– Database design and generation tool
– Model driven approach
– Models:
– Logical
– Data types
– Dimensional
– Relational
– Data Flow diagrams
– Physical models
Features

Features – Other types of models

– Importing – from Designer, Erwin (XML) and more
– Version Support – team development (Subversion)
Features – import your model, put it in your VCS

Bring some color to your designs!

Features – Logical Models

Features – Logical Models – Actual Footage ! Corporate Identity applied !
Barker (Oracle Designer)

Features – Logical Models – Actual Footage ! Corporate Identity applied !
Bachman
Barker (Oracle Designer)
Information Engineering

– Subviews can be used to represent objects related to given
subject area
– Subviews can be nested(linked) thus allowing to build
network (or hierarchy) of related subviews – navigation
between linked subviews is supported
Features - Subject Area Management

Features - Subviews

Do you have naming standards ?
Get some!

– Name structure for elements in Logical and Relational
models
– Model level restrictions for – name length, possible
characters, used letter case
– Name translation during engineering between logical and
relational models
– Naming templates for table constraints and indexes
– Prefix management
Features – Naming Standards

Right mouse menu on design
properties->settings->naming standard

– Supports validation rules;
– Easy exchange and synchronization of domains;
– Assignable to group of attributes and columns
in different models;
– Set “Default value” property at domain level. This can be
updated at column/attribute level.
Features - Domains
Example:
domain = Country Codes
mandatory = True
values = (NL = The Netherlands, UK = Great Britain)
default = NL

Features – Object Model
The design is stored as an object model
That can be manipulated programmatically
(which is NOT the subject of this presentation)
That can be queried programmatically
Which enables you to synthesize PL/SQL scripts based on the
design and each detailed property of the design

Relational Model AFTER some tuning ….

Design import needs tuning? Transform !

– A few transformation scripts are pre-supplied
– Like adding default columns to a range of tables, or
– Like re-ordering columns after engineering from logical
– Add your own transformation scripts
Features – Relational Models – Transformation scripts

Features – Relational Model – Custom Transformation Scripts

Oracle Nashorn

Code Generation
Code
Generation

Transformations is your Code Generator

– Add a custom transformation
– Set it up to output modeled design to the file system
– Model design properties
– Dynamic properties
How to generate code

// Code shown below is JavaScript //
application_name = model.getName();
appfolder = "Documents/Oracle/SDDM/sql/"+application_name+"/";
Basic setup: generated code output folder

– C:Oracledatamodelerdatamodelerxmlmetadatadoc
– SQLDeveloperDataModelerScripting.docx
– Index.html
Object Model definition

runFile = new java.io.FileWriter(appfolder+appname+ "_CREATE_ALL.sql");
run = new java.io.PrintWriter(runFile);
run.println("-----------------------------------------------------------");
run.println("-- Version : 1.0.0");
run.println("-- Proces : Zorgsturing");
run.println("-- File-name : <app_alias>_CREATE_ALL.sql");
run.println("-- Creator : Rob van den Berg");
run.println("-- Creation date : "+ today);
run.println("-- Description : Master create script");
run.println("--");
Basic setup: include a master script

Created Master Script

// Code shown below is (PL/)SQL //
/*
Maintain table level constraints on ZST_VERTALINGEN_MPG
Change History
Who When What
---------------- ---------- --------
Rob van den Berg 12/05/2016 Creation
*/
-- define check constraints
alter table ZST_VERTALINGEN_MPG add constraint ZST_BR_VMP003_TPL check
(datum_einde is null or (datum_ingang <= datum_einde));
Implementation of Tuple Rule
Generated script
ZST_VMP_CON.sql

Definition of Tuple Rule

tables = model.getTableSet().toArray();
for (var t = 0; t<tables.length;t++){
// check constraints
tccs=table.getCheckConstraints().toArray();
for (var n=0;n<tccs.length;n++){
con.println
( "alter table “ + table_name + " add constraint “ +
table.getProperty(tccs[n].getName()) +
" check (" + tccs[n].getRule() + ");"
);
}
}
Let’s generate customized script layout for check constraints

– typical Entity Rule “rows should not OVERLAP”
– Which typically presumes data definition of
– Column start_date NOT NULL
– Column end_date
– Some unique key including start_date
next to (optional) columns identifying the group
– Analist would phrase the rule like
“Thou shalt not enter any conflicting time period (for the
group of tuples identified by X, Y, Z”
Definition of Entity Rule

Definition of Entity Rule: specify the name identifying the rule

/*
Maintain Table ZST_VERTALINGEN_MPG
…
…
--define unique key(s)
alter table ZST_VERTALINGEN_MPG add constraint zst_vmp_un1 unique
( bte_id
, mpg_code
, oms_extern
, datum_ingang
);
Implementation of Entity Rule: unique key including start_date
Generated script
ZST_VMP_TAB.sql
START_DATE
OVERLAP can still occur

create or replace trigger ZST_VMP_BIR
before insert on ZST_VERTALINGEN_MPG
for each row
begin
-- support insert change event
ZST_VMP_PCK.trg_bir
( p_id => :new.ID
…
, p_datum_ingang => :new.DATUM_INGANG
…
, p_datum_einde => :new.DATUM_EINDE
);
end;
/
Implementation of Entity Rule
Generated script
ZST_VMP_TRG.sql
START_DATE
END_DATE

– Triggers generated within each trigger definition file:
– Before insert, update, delete statement
– After insert, update, delete statement
– Same for row triggers

procedure trg_ais
is
begin
check_br_vmp002_ent;
…
end trg_ais;
Generated script
ZST_VMP_PCK.sql

…
procedure check_br_vmp002_ent
is
-- Check if any time overlap check does not get violated
-- find record overlapping in time
cursor c_overlap
( v_not_id in ZST_VERTALINGEN_MPG.ID%TYPE
, v_bte_id in ZST_VERTALINGEN_MPG.BTE_ID%TYPE
, v_mpg_code in ZST_VERTALINGEN_MPG.MPG_CODE%TYPE
…
…
Generated script
ZST_VMP_PCK.sql

Generating code
– Is efficient
– Follows standards and guidelines
– Leads to maintainable code. No exceptions.
Conclusions

Agenda
Improvement
s

Improvements – documentation

Generating Code with Oracle SQL Developer Data Modeler

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (20)

Ähnlich wie Generating Code with Oracle SQL Developer Data Modeler

Ähnlich wie Generating Code with Oracle SQL Developer Data Modeler (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Generating Code with Oracle SQL Developer Data Modeler

Hinweis der Redaktion