SQWareRepository:general: Difference between revisions

Revision as of 08:53, 1 June 2015

Presentation

SQWareRepository™, also known technically as expDbDb®, is the repository module, and stores rdbms indicators.
It manage the repository and the database indicators ...

This module has is managed in a MySql database.

Links to different plugins of SQWareRepository™ module :

Download the latest stable versions
Installation guide for SQWareRepository™

General architecture diagram SQWareRepository™ (when the SQWareProduction™ module is locally installed)

naming convention

All objects are named with prefixes:

tsqw_% : for tables
isqw_% : for index
isqw_%_u : for uniques
isqw_%_pk : for primary key

Warning:
Do not change the standard tables of the tool. For your custom objects, use another name convention than dbSQWare.

This will facilitate version upgrades.

@@ Line 1: / Line 1: @@
 == Presentation ==
 SQWareRepository™, also known technically as expDbDb®, is the repository module, and stores rdbms indicators.<br>
-It manage the repository and the database indicators (this is actually a schema or database)..<br>
+It manage the repository and the database indicators ...<br>
 <br>
-This module has one part per RDBMS managed. There is no 'core' part, each type of RDBMS is independent.
+This module has is managed in a MySql database.<br>
-There is still a consistency between all these MCD, you will find for example the referential table tsqw_Repository in each.<br>
-Each scheme is managed in the same type of RDBMS that managed to avoid client deployment problem (Oracle in Oracle, Sybase, Sybase ...). One exemption is Ingres, Ingres indicators are managed in a MySql database.<br>
 <br>
 Links to different plugins of SQWareRepository™ module :

SQWareRepository:general: Difference between revisions

Revision as of 08:53, 1 June 2015

Presentation

General architecture diagram SQWareRepository™ (when the SQWareProduction™ module is locally installed)

naming convention

Navigation menu

Search