This diagram describes how
the core Rubicon components and links (or drivers) fit into a database application.
|
| Application Code |
| | |
| |
|
| |
Core
Rubicon Components
TrbMake, TrbUpdate, TrbSearch, etc.
These components make, update, and search Rubicon indexes. |
| | |
| |
| |
|
|
|
| |
Text
Link
Rubicon component used to read the Text table via a specific database
engine |
Words
Link
Rubicon component used to create and access the Words table via a specific
database engine |
| | |
| |
| |
Database
Engine
TTable, TQuery, ADO, Advantage, Apollo, DBISAM, DOA, FlashFiler,
NexusDB,
IBObjects, IBX, ODBC Express, Topaz |
| | |
| |
Text Table
The table being indexed. Must contain a unique integer field used by
Rubicon to keep track of the record's location. |
Words
Table
Table created by the Words link that stores the Rubicon indexes.
Usually the same table format as the Text table. |
For more detailed information, please
see:
TrbMake: how Rubicon
indexes are created
TrbUpdate: how Rubicon
indexes are maintained
TrbSearch: how Rubicon
indexes are searched
|
