Difference between revisions of "Template:SQWareRepositoryPresSgbd"
Expdbtools (talk | contribs) (→Presentation) |
Expdbtools (talk | contribs) (→Naming convention) |
||
| Line 9: | Line 9: | ||
== Naming convention == | == Naming convention == | ||
All objects are named with prefixes: | All objects are named with prefixes: | ||
| − | * | + | * tsqw{{{1}}}_% : for tables |
| − | * | + | * isqw{{{1}}}_% : for index |
| − | * | + | * isqw{{{1}}}_%_u : for uniques |
| − | * | + | * isqw{{{1}}}_%_pk : for primary key |
<br> | <br> | ||
{{Warning_objets}} | {{Warning_objets}} | ||
<br> | <br> | ||
Revision as of 14:49, 8 August 2015
Presentation
It is the repository module, and stores rdbms indicators for {{{1}}}.
It's a {{{1}}} {{{2}}}. It is currently the only type of supported RDBMS for dbSQWare® repository for {{{1}}}.
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.
The first task is to insert the informations of {{{1}}} {{{3}}} in the repository. It's tsqw_Repository table which contain basic informations of {{{3}}} to manage.
[[Installation#SQWareRepository for {{{1}}} | Installation guide for SQWareRepository™ for {{{1}}} ]]
Naming convention
All objects are named with prefixes:
- tsqw{{{1}}}_% : for tables
- isqw{{{1}}}_% : for index
- isqw{{{1}}}_%_u : for uniques
- isqw{{{1}}}_%_pk : for primary key
