The Database ribbon bar exposes the project's connections to remote object stores. It is split into two sections: gSpace database for the native g-Space multi-user server, and gPlatform database for connections to Geomage's gPlatform data service. Each section offers its own connect, import and export buttons.
gSpace database
Operations that act on the native g-Space project database (used for multi-user work).
•Connect — opens the Database connection wizard where the user supplies the server address and credentials needed to attach the current project to a remote gSpace repository. See Multi-user mode for the full workflow.
•Sync settings — opens the Sync settings wizard described below; selects which project objects participate in database synchronisation.
•Import data — fetches objects (wells, horizons, seismic, polygons, …) from the connected gSpace database into the current project.
•Export data — uploads local objects back to the gSpace database; the same dialog is used by the per-object Send to DB context action.
•Delete data — removes selected objects from the remote database.
•Clear references — breaks the link between local objects and their remote counterparts without touching the remote data. Useful when a project is forked into a standalone copy.
gPlatform database
Operations that act on Geomage's hosted gPlatform data service.
•Connect — opens the Connect to gPlatform database wizard described below.
•Import data — fetches datasets from gPlatform into the current project.
•Export data — uploads selected project objects to the configured gPlatform account.
Connect to gPlatform database
This dialog captures the connection parameters used for every subsequent gPlatform import/export. The wizard validates the input before allowing the project to store credentials.
Input fields:
•Hostname — DNS name or IP address of the gPlatform server.
•Port — TCP port used by the gPlatform endpoint.
•Database — name of the target database on the server.
•Username / Password — account credentials.
Actions:
•Test Connection — tries to reach the server with the supplied parameters and reports success or failure without saving them.
•Connect — stores the credentials in the project and opens the connection for the current session. Invalid input fields blink red until corrected.
Sync settings wizard
The Sync settings wizard controls the scope of database synchronisation. It lists every syncable object in the project (horizons, faults, wells, polygons, maps, …) and lets the user pick which ones to push or pull.
Main controls:
•Search field — filters the object tree by name.
•Object tree — hierarchical list grouped by data type (Horizons, Faults, Wells, Polygons, Maps, …), each entry with a checkbox.
•State filters — show only objects in a given sync state: Created, Modified or Deleted.
•Total size indicator — estimates how much data the current selection represents before uploading.
•Context menu — batch check / uncheck all objects of a given type.
Object revision list
Most database-linked objects expose an Object revision list command in their context menu. It opens a table summarising every revision of the selected object stored on the server, with six columns: timestamp, user, revision ID, object state, comment (editable) and action.
Common operations:
•Edit a comment in-place to document why a revision was produced.
•Rollback — revert the local object to a previous revision.
•Export the visible history through the window's toolbar to share an audit trail with other users.
See Also