DataClass

Concept: Version

Abstract

A version is a single revision to a database's design. The proper way to arrange construction steps for a database is in a linear sequence that corresponds with the actual versions that could be deployed into production.

Body

Production databases are typically upgraded one version at a time. That is, every time you release a change to the database, you create a new version of that database. Why not embrace the fact that the most important database instances you will ever touch are always upgraded one step at a time?

DataClass helps you arrange the construction steps for a database into version deltas (transitions). Each delta explains how the database must be upgraded from a version's predecessor to that version. When a database instance is built, DataClass inspects that instance to see which transitions have been applied and which still need to be executed.

Those transitions which have already been executed are audited in order keep your database class somewhat tamper-resistant. The remaining transitions are executed in the correct order.

Related Use Cases

• Specifying design separately from construction
• Simple versioning and build management
• Tamper-proofing database classes
• Building a database
• Organizing database versions
• Getting compiler feedback on your database design
• Keeping clients coupled to the current version
• Leveraging a version's proxy in a client
• Transition testing

Related Concepts

• Class of databases
• Tamper-proofing
• Transition

Other Actions

documentation | all examples | use cases | concepts | keywords