| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 841.1 | Use anything that can access Rdb | BSYBEE::EGOLF | John C. Egolf LKG2-2/T02 x226-7874 | Mon Mar 25 1991 17:41 | 8 |
| Tom,
Once you've EXPORTed the data to Rdb, you can use *ANY* tools
to move it elsewhere. You can write a Cobol program or a Bliss
program, you can use any tool that can access Rdb. You do not
have to use DTR.
JCE
|
| 841.2 | Documentation? | LTLKNG::TAZBOY::ZIGLER | Tom Zigler DTN:432-7541 | Tue Mar 26 1991 17:43 | 14 |
| Re: .1
Yes, but does the documentation provide the end user with the necessary
and sufficient information to be able to know HOW to apply the third
party front-end user interfaces? For example, is there VAX Rdb/VMS
schema information necessary to know and provided in the documentation
to allow me to access the Rdb data using a third party database access
tool such as FOCUS? I have gotten the impression from other replies in
this conference that it took some doing for folks to figure out how to
use even DECdecision, for instance.
Please advise.
\Thanks in Advance
|
| 841.3 | No documentation about structure of relations | TOOK::R_LANE | | Thu Mar 28 1991 12:20 | 35 |
| > For example, is there VAX Rdb/VMS schema information necessary to know and
> provided in the documentation to allow me to access the Rdb data using a
> third party database access tool such as FOCUS?
The current Exporter documentation does not provide the information about
the created relations (tables).
There are a few problems associated with having to provide the information
about the relations in the Exporter documentation. The Exporter creates
the relations "dynamically" based on entity attribute information in the
MCC dictionary. The data in the MCC dictionary is subject to change.
Also, the Exporter creates a relation for each class of entities (NODE4,
NODE4 LINE, NODE4 CIRCUIT, ...). There would have to be quite a lot of
documentation to cover all the possibilities.
It's quite easy for a user to determine the structure of the relations
created by the Exporter using the available database access tools. For
example, using interactive SQL, the user can determine the structure of a
relation as follows:
$ SQL
SQL> DECLARE SCHEMA FILENAME <file spec>;
SQL> SHOW TABLES
... tables (relations) in database are listed ...
SQL> SHOW TABLE <table name>
... displays table structure ...
where <file spec> is the file specification for the Rdb database and
<table name> is the name of the relation.
---
Roy
|
| 841.4 | document .3 and the algorithm used | TOOK::DITMARS | Pete | Fri Mar 29 1991 09:37 | 5 |
| I got a brief verbal description (from Sam) of the algorithm that Exporter uses
to create the table definitions dynamically. If it doesn't already, the
documentation should contain the method for determining the structures
(as given in .3) and maybe the explanation of how the tables are
constructed (as dictated by Sam).
|