Ultimate Database System Overview
The Ultimate Database is built around a type of neural network of data comprising of objects and relationships.
It can hold basic data and structured information on any subject, including itself.
It has built in version control, audit trails, security structure, user interface and development environment.
It has a comprehensive development language designed to get the most from the data as quickly and easily as possible.
The Database is made up of six main types of Object tied together by relationships.
| Object Type | Description |
|---|---|
| Application Lists | Application lists are used to arrange the data. They have no real significance regarding the data content although components can be assigned to them to affect the way the data is displayed. |
| Data Lists | Data lists are, as their name suggests, used to hold data. Although it could be argued that everything is data, Data Lists are for the more obvious content such as a list of Customers or Orders. |
| Items | Items are where all the action happens. They can be any number of different things. A Company record, an Order, a Web Page, some CSS or a template describing how some data is to be displayed. |
| Relationship Definitions | Relationship Definitions are the descriptions of the string that ties all the data in the Data Lists together. They can be used to define the relationship between a Company and their Contacts, the items in a Menu Structure or the components required to display certain item types. |
| Comments | Comments play a fairly minor role in the proceedings as they are really just a convenient structure for forums or a comment area at the bottom of the page. |
| Groups | Groups are simply a convenient way to create a collection of items. They are generally used for grouping menu items together such as the Items under "UDB Documentation" on the main navigation menu at the top of this page. |
Every object has an ID. These IDs are used throughout the system to reference the objects.
For example, you might have a data list (id = 1001) to hold photographers.
You might then have another data list (id = 1002) to hold photographs.
These could be linked together with a relationship (id = 1003) from the photographers (1001) to the photographs (1002).
Then, when displaying a photographer, you can use the relationship to access the photos.