Overview of Objecteering SQL Designer

Introduction

Welcome to the Objecteering SQL Designer user guide!

Objecteering SQL Designer is used to couple Objecteering with RDBMS, and allows you to use a model to map the persistence of classes into a relational database.

Persistence characteristics are defined interactively by simply annotating different model units using tagged values, whilst the generator creates tables, constraints and triggers.

Using Objecteering SQL Designer

RDB application modeling is illustrated as shown in Figure 1 below.

Figure 1. The two stages in the modeling of an RDB application

It is possible to pass directly from the analysis model (also called the logical model) to the physical model, by annotating the analysis model and applying transformation patterns to it, in order to generate the corresponding physical model.

The physical model obtained can also be annotated, so as to define specific SQL generation characteristics.

Operations are carried out using DDL (Data Definition Language) scripts. Here, SQL is used.

The RDBMS currently covered are Sybase, Oracle and SQL Server.

Specific features of the RDBMS target

Beyond the mapping provided as standard, you can annotate your modeling using tagged values, which allow the specification of production towards the relational, using the characteristics of the different RDBMS available on the market. For example, it is easy to group tables into clusters, or to add triggers and constraints.