tcm2sql 1.0.0

What is this?

tcm2sql is a tool for generating SQL commands from a tcm static structure diagram (SSD). It was developed by Christian Zagrodnick for gocept to generate some large PostgreSQL databases out of diagrams.

This diagram type is normally used for object structures in UML. If you are familliar with the UML notation, you should get the tcm2sql conventions fairly fast into your brain.

Renderers can be plugged in to tcm2sql quite easy. Currently there is only a renderer for PostgreSQL. It creates PostgreSQL compatible create table and related queries. The documentation is mostly based on PostgreSQL terms. There is a section which deals with other renderers.

In prior versions there were also:

• DBObjects – for creating some code which might be useful if you are using DBObjects.

• Prolog – for creating Prolog terms.

Those have been removed because of vast changes in tcm2sql’s internal API and no actualy need for them. If you like to see those or others please contact me.

There is also a mode for generating the difference between two SSDs. This allows to semi automatic updating of databases.

TCM can be obtained from University of Twente. There is versionavailable on Debian, too.

Thanks to Christian Theune for reviewing the documentation.

The conventions

You might want to open an Example*.ssd in the doc directory of this package.

Double Class Boxes and Triple Class Boxes are used for tables. As in UML the top is for the name, the middle for the attributes. The bottom part is used for constraints in tcm2sql.

Constraints

As stated above, what the operations are in UML, are the constraints in tcm2sql.

Constraints have a similar definition as attributes:

<Constraint> ::= <ConstraintName>: <ConstraintOperation>

For example:

invalidFoo: check (foo>47) dupeFooBar: unique (foo,bar)

To avoid very large boxes in the diagram you also have the possibilty to add constraints using the annotation of your table. It then has to be prefixed by an questionmark (?). Since tcm has no indicator for boxes which have an annotation you might write <ext> as constraint, which is just ignored and is a good remember for yourself.

<Constraints> ::= [[<Constraint>|”<ext>”]n]*

Relations

In UML there are different types of relations between classes, which I tried to adapt to PostgreSQL.

Implemented in tcm2sql:

• Aggregation (white diamond)

  results in an on delete set null

  The diamond has to be connected to the table with the referenced PRIMARY KEY.

• Composition (black diamond)

  results in an on delete cascade on update cascade

  The diamond has to be connected to the table with the referenced PRIMARY KEY.

• Generalisation (arrow)

  results in inherits (foo) See PostgreSQL documentation for details.

  The parent table is where the arrow points to.

• Binary relationship

  results in an ordinary relation between two tables.

  You have to write a 1 on one end in the cardinality field. This is where die PK resides.

So what’s the ~ for?

Within a table every FOREIGN KEY has to be prefixed with the ~. There are two ways for assigning a row to a relation.

1. Write the FK’s name as ROLE on the relation.

2. Name it <Othertable>_<OthertablePK>

How to reference a composite primary key?

Make a single relation between the tables and put the names of the foreign keys komma separated into the “role name” of the foreign key side of the relation.

Views and Private Attributes

For every table a view sv<TableName> is created with only public attributes. If you need access to the database with ODBC but cannot allow access to all attributes you just mark the private attributes with - and let ODBC only access the views.

The modes

Using multiple ssd files to create a single database

As the database grows you get more and more junctions. Furthermore tcm allows only six pages which become full. To avoid both problems you can split your database into several files.

The file you pass as parameter to tcm2sql is started with. To have a connection to another ssd file you create a class node with a stereotype. The stereotype is the relative (to the master ssd) or absolute file name of the ssd to be included. The table name references the actual table in the included ssd. See ExampleInclude*.ssd for an expamle.

It is possible to build include circles and including forth and back without any problem.

Examples

There are two example ssds, just try tcm2sql on them.

References

1.0.0 (2010-12-14)

• Eggified package.

• Added entry point for console script.

0.9.2 (2006-10-18)

• Restructured renderer classes to make it easier to write renderers for other database managenemt systems.

• Better handling for serials and bigserials: Now they are always written as integer with default + creation of sequence. (This makes updating of tables possible which have serial columns.)

• Added commandline option –no_views to not generate views for the tables.

• Made usage help a bit nicer.

0.9.1 (2005-03-31)

• Multi column foreign keys

0.9 (2003-09-13)

• splitting database to several diagrams (see README for documentation)

• requires Python 2.2

• complete rewrite of ssd file reader

• large changes on internal data structures

• code is much more readable

• DBObjects and Prolog renderer removed; they had to be changed to fit into the new structure but there is no need for them right now.

0.04 (2002-08-02)

• prolog renderer

• DBObjects renderer (quite useless)

• fixed the create/drop sequence bug (bug #374)

• Added logging tables for Postgres

0.03 (2002-03-30)

• Works with python2.1 now

• some minor fixes

0.02 (2002-02-13)

• first public release