Voyager: A Model Based DB Browser

Asset Enterprise Technologies

Database browsers abound in the market place. Then, why does Voyager deserve your precious time? Voyager radically alters the database browser paradigm by combining query by example and model based user interface generation. As Voyager user one would never to write another line of code to manage records in a relational database. Voyager scales with number of tables, records and users. Voyager ends graphical user interface generation as we know it. Users simply define the model for a given database and in minutes can browse the table as intuitively as a custom graphical user interface.

Some illustrative screenshots

When Voyager is invoked a tool bar as shown here appears. Other tools can easily be included.
An organizational entity model is divided into divisions and ordinary relational tables. We have introduced division as a grouping mechanism so that we can restrict access by division. In the screen shown here GovPX has four divisions, namely,

  1. Information Assets
  2. Technology Service
  3. People
  4. Treasury

This particular user does not have access to divisions 1, 2 and 3.
A table is presented in two areas. One of them is the QBE area (Query By Example) and it allows users to specify a record partially and retrieve all records from the corporate table that match that criteria. The other one is the multi-record preview area which will be discussed next. Notice that just above the QBE area is the toolbar with which the usual db operations can be easily performed. Here Corporate is one of the tables in the Treasury division.
Given an example (partial record), matching records are fetched and presented in the preview area. Selectively, some or all the columns can be displayed in this preview area. When a row in the preview area is selected the QBE area is populated with the complete record.