Database Repository

Topic updated 20-6-2007

The Database Repository contains database schema metadata to be used in applications created with GenWise. The Database Repository serves the  following purposes:

Abstract view of the database schema, hiding specifics of different database types.
Setting field names, descriptions and help texts to be used in the user interface.
Setting names of database objects as seen by application layers.
Enrichment of the database schema. For example with Custom Views which make client side joins.

A Database Repository can have one or more Datastores. Each Datastore contains a connection to a specific database plus the metadata of that database.

Datastores use Database Providers to create connections to specific databases. For each supported database there is an associated Database Provider that provides a connection configuration screen. It is also the Database Provider's task to map the physical database structure to the Database Repository's abstract view of the database schema.

 

Database schema enrichment

In addition to the control over naming and labeling for all application layers, the Database Repository makes it possible to enrich the database schema in the following ways:

Define Validations to be implemented in application layers.
Create Custom Views, which act like database views not physically defined in the database.
Define relations not physically present in the underlying database (useful when using legacy databases).

 

Database schema synchronization

The transfer of database schema information between databases and the Database Repository can go both ways.

The Database Repository can import schema from databases, and keep its metadata up to date using its Compare Schema function.
Database objects can be defined in the Database Repository, and then added to a database using the SQL Script creation and execution tools.

 

Application development features

The Database Repository has the following features that can help application developers to be productive.

The Mass Column Editor gives a spreadsheet-like view of all database fields of a Datastore, where all field names, descriptions and help texts can be set.
Browse Data screen to inspect data content of tables and views.
Adhoc SQL screen with code completion for execution of SQL statements.
Datastore Diagram for visual representation of objects and their relations in a Datastore.
Create SQL Scripts for all tables or per single table in the Datastore.

 

Datastore Diagram example

DatastoreDiagram