Re: RTB Schema

From: Rene Santegoets

Date: 26 Nov 2001

Jurjen wrote:
> Geoff wrote:
>> (..snip..) if I only want the
>> include files and RUN's in the XREF, then I only have to
>> create records for two tags instead of all of them.
> Yes, I like that.

We've been doing this. And also for usage of table (CRUD,
create-read-update-delete); usage for field(read-update),
usage for index, usage sequence.....
All those tag-records are very small. The only info you want
are the 'where-used' reports. For that you need a buch of
32-byte tag-records with 2 indexes.
The database size has never been a problem.

The 'engine' could easy read and from XREF and from a table
in the RFB database (If RTB stores the complete XREF.)

Ren� Santegoets.

----- Original Message -----
From: "Jurjen" <ae0b643c-b939-8280-de11-700348b430b8>
To: <>
Sent: Monday, November 26, 2001 8:42 PM
Subject: RE: RTB Schema



Geoff wrote:
> (..snip..) if I only want the
> include files and RUN's in the XREF, then I only have to
> create records for two tags instead of all of them.

Yes, I like that.

> In order to proceed with this XREF thing I think we better come
> to a decision about using or not using the RTB schema fairly soon.

Well, as a RTB user I have no choice: the application must be compiled by
RTB and the XREF must be stored in the RTB database. It would be sad if the
new tool would require us to compile the application a second time and store
XREF in a second database.

What if the tool would have a "data layer" in two versions: the version for
RTB users and the non-RTB version?
The non-RTB version would save and find data in your optimized database, the
RTB version would find data in the RTB database (and not save anything since
the roundtable desktop takes care of that).

Actually, the version for RTB users will probably still connect to the new
database for some tool-specific data, like data extracted by proparse,
warnings from prolint, links to pages generated by AutoDox (see
http://www.joanju.com/autodox/, or whatever hooks onto the tool.

Jurjen.