Stereotypes

Introduction

Objecteering defines stereotypes, used to designate certain objects as being concerned by the generation of Objecteering SQL Designer code. In this way, a class causing an error that has occurred will be treated as an exception, if it bears the <<XXX:exception>> stereotype.

Stereotypes on a constraint

The ... stereotype	is used to...	SQL
<<notNull>>	indicate that the column must have a value.	NOT NULL
<<null>>	indicate the column may not have a value.	NULL
<<unique>>	Indicate that the values taken by the attribute must be unique for the entire table.	UNIQUE
<<check>>	associate a "check" type constraint to an attribute.	CHECK
<<rule>>	associate a "rule" type constraint to an attribute (Sybase).	CREATE RULE

Stereotypes on a class

The ... stereotype	is used to...	SQL
<<procedureClass>>	specify that the class only contains stored procedures.
<<table>>	indicate that the class is an SQL table.
<<sqlView>>	describe an SQL view.
<<externalTable>>	indicate that the class is an SQL table outside the current SQL schema.	<<externalTable>>

Stereotypes on an artifact

The ... stereotype	is used to...	SQL
<<database>>	indicate the creation of a database. The implementation of artifacts is used to model dependencies between databases, and their deployment.

Stereotypes on an operation

The ... stereotype	is used to...	SQL
<<createView>>	indicate that the operation contains SQL code, placed on an "sqlcode" note, allowing a view to be created.
<<trigger>>	indicate that the operation is a trigger.	CREATE TRIGGER
<<storedProcedure>>	indicate that the operation is a stored procedure.	CREATE PROCEDURE

Stereotypes on a package

The ... stereotype	is used to...	SQL
<<schema>>	indicate that the package is a schema.
<<database>>	indicate that the package is a database. This stereotype is only used in the physical model.
<<sqlPhysicalModel>>	indicate that the package is a physical model.