Database Browser

Carlo Boarotto

OHS

08-Sep-2000

Database Browser: Why?

Some Phase 1 and Phase 2 tools have the same database browsing functionalities:

• query the database
• display the results in a table
• show detailed views of selected rows
• operations on:

set of rows

single row

Database Browser: Overview

What is:

A generic database browser component for database browsing applications.

Objective:

• Set of classes defining a generic GUI application to browse generic databases.
• Build SQL queries dynamically by means of a user designed GUI.
• Display the result retrieved running the queries on the database.

Database Browser: Requirements (1)

1. Queries should display results as they are retrieved, without waiting for the full result set to be retrieved (unlike P2PP 1.x and OT 1.x browsers).
2. User should be able to interrupt (break) the query at any time (also unlike PHRS and P2PP 1.x browsers).
3. User should be able to preview the number of rows retrieved according the selection criteria, without running the query itself.
4. Support for operator type-in in the Select widgets.

Example: Users can enter strings like
> 5000
!= Executed
like `abc'

 

5. It should be possible to display database data according to some programmer defined formats (e.g. target coordinates are now stored in the tables as integers and should be displayed as <degrees / hours>:<minutes>:<seconds>).

Database Browser: Requirements (2)

1. Sorting/1: re-sort the in-memory result set, without executing a new query.
2. Sorting/2: sorting area buttons have three states according to the "ORDER BY" clause's values: none (not selected), ascending and descending.
3. Editing/1: modifications to the data performed in the detail area should be reflected automatically in the summary area, without the need for a new query.
4. Editing/2: modifications to the data can be performed directly in the summary area. Options: auto-saving of udated rows, or "Save" button.

Database Browser: GUI layout