Difference between revisions of "Main:Database index"

From Memento Database Wiki
Jump to navigation Jump to search
m
Line 2: Line 2:
 
{{banner-menu}}
 
{{banner-menu}}
  
==Preamble on database terminology ==
+
==Memento & Industry database terminology ==
 
This is to get us on the same page regarding terms Memento users have used previously versus the terms chosen by Memento for its products. [[#The Database index, allowing quick access to Memento Database information|Jump to the database index]]
 
This is to get us on the same page regarding terms Memento users have used previously versus the terms chosen by Memento for its products. [[#The Database index, allowing quick access to Memento Database information|Jump to the database index]]
  
Line 9: Line 9:
 
'''''Yada'''''
 
'''''Yada'''''
  
The Memento Database application comprises ''libraries'' (often known outside Memento as tables), ''entries'' (often known outside Memento as rows), and ''fields'' (often known outside Memento as columns). A common generic term, recognized everwhere for either entries or rows is ''records''.
+
{| class="wikitable" width="100%"
 +
! Term !! Common industry terms !! Relational terms !! Memento terms !! Generic terms
 +
|-
 +
| style="width: 10%; text-align:center" | '''''Field'''''
 +
| style="width: 20%" | A type of field instead of ''field type''. A '''''field''''' is also used to refer to the data (datum, in actuality) that may have been entered into a ''field''.
 +
| style="width: 20%" | A '''''field''''' the name of a column in a table or library
 +
| style="width: 20%" | '''''field'''''
 +
| style="width: 30%" | ''domain'' when discussing the ''data structure'' and the name of a datum, or the data as displayed in a library entry, a table row, or a database record.The term ''field'' is universal. It is sometimes used to refer to the ''domain'' or ''type'' of field, or ''field type''.
 +
|-
 +
| style="width: 10%; text-align:center" | '''''Record'''''<br/>or<br/>'''''Row'''''<br/>or<br/>'''''Entry'''''
 +
| style="width: 20%" | Like ''library'', '''''record''''' is generic term referring to an ordered set of data representing ''the data used by a user base for a given scope''.
 +
| style="width: 20%" | A '''''table''''' is a specific term for s set of
 +
| style="width: 20%" | A '''''Record''''' is an ordered set of fields of data, treated as a unit within a ''database'', ''table'', or ''library''.
 +
| style="width: 20%" | '''''Record''''' is a general database term not specific to any particular database product.
 +
|-
 +
| style="width: 10%; text-align:center" | '''''Table'''''<br/>or<br/>'''''Library'''''<br/><small>or<br/>''(sometimes Database)''</small>
 +
| style="width: 20%" | A collection of ''records'' containing data.
 +
As ''record'' is a generic term, it may be identified by a possibly unique (unspecified) means.
 +
<br/><br/>A ''record'' may be identified '''''in other tables''''' by inclusion there of this (same) key, called a secondary key.
 +
| style="width: 20%" | A collection of ''rows'' containing data.
 +
A row may be identified by a possibly unique primary ''key''
 +
<br/><br/>A row may be identified '''''in other tables''''' by inclusion there of this (same) key.
 +
| style="width: 20%" | A collection of ''entries'' containing data.
 +
A entry may be identified by a possibly unique entry name.
 +
<br/><br/>An entry may be identified '''''in other libraries''''' by use of a Link to Entry field.
 +
| style="width: 30%" | Use '''''table''''' outside Memento. Some people outside Memento unfortunately still use ''database'', where we would use ''library''.
 +
|-
 +
| style="width: 10%; text-align:center" | '''''Database'''''
 +
| style="width: 20%" | One or more related tables or libraries
 +
| style="width: 20%" | One or more related tables
 +
| style="width: 20%" | One or more related libraries
 +
| style="width: 30%" | Use '''''table''''' outside Memento. Some people outside Memento unfortunately still use ''database'', where we would use ''library''.
 +
|}
 +
 
 +
The data used by a user base for a given scope
 +
 
 +
In Memento, use library. In the relational world, use table. Table is the most gernerally recognized term. (Some people outside Memento unfortunately still use database.
 +
Database One or more related tables or libraries One or more related tables One or more related libraries Use table outside Memento. Some people outside Memento unfortunately still use database, where we would use library.
 +
 
 +
The Memento Database application comprises ''libraries'' (often known outside Memento as tables), ''entries'' (often known outside Memento as rows), and ''fields'' (often known outside Memento as columns). A common generic term, recognized everywhere for either entries or rows is ''records''.
  
 
In the Memento forum, "field" and "record" are often used and "column" and "row" is seldom used. So, it's best to stick with either Memento's "entry" (since it's their forum, after all), but when others use or seem to prefer the database industry's "record", we'll all know what is meant by that, and we can accommodate them when interacting with them, message by message in the forum.
 
In the Memento forum, "field" and "record" are often used and "column" and "row" is seldom used. So, it's best to stick with either Memento's "entry" (since it's their forum, after all), but when others use or seem to prefer the database industry's "record", we'll all know what is meant by that, and we can accommodate them when interacting with them, message by message in the forum.
Line 18: Line 57:
 
When a user's objectives are so small that a single library is enough, then in that case the database is the library. However, when a user's objectives require that libraries be linked together to accomplish the objectives, now the entire set of linked libraries constitute the database. That's why, whenever we go into Edit Library > Export to create a .template file, there's an option to include linked libraries. This makes the template a database export rather than merely a library export. For more on database exports, see [[How:Export a database|Export a database]].
 
When a user's objectives are so small that a single library is enough, then in that case the database is the library. However, when a user's objectives require that libraries be linked together to accomplish the objectives, now the entire set of linked libraries constitute the database. That's why, whenever we go into Edit Library > Export to create a .template file, there's an option to include linked libraries. This makes the template a database export rather than merely a library export. For more on database exports, see [[How:Export a database|Export a database]].
  
Libraries can be linked so they can work together as a database. So, each library has a structure of fields & other things (see below for what things make up its structure), and each database has a structure of libraries & links between them (see About:Database structure#Examples for an example).  
+
Libraries can be linked so they can work together as a database. So, each library has a structure of fields & other things (see below for what things make up its structure), and each database has a structure of libraries & links between them (see About:Database structure#Examples for an example).
  
 
== The ''Database index'', allowing quick access to Memento Database information ==
 
== The ''Database index'', allowing quick access to Memento Database information ==

Revision as of 15:24, 11 December 2021

« Page as of 2021-11-04, editions Mobile 4.10.2, Desktop 1.10.2 »

Template:Banner-menu

Memento & Industry database terminology

This is to get us on the same page regarding terms Memento users have used previously versus the terms chosen by Memento for its products. Jump to the database index

Memento terms and database industry terms

Sometimes some of us tend to use one set of terms for things, and some might use another set of terms for the same things, like "record" or (less often) "row" for a Memento entry and ... Yada

Term Common industry terms Relational terms Memento terms Generic terms
Field A type of field instead of field type. A field is also used to refer to the data (datum, in actuality) that may have been entered into a field. A field the name of a column in a table or library field domain when discussing the data structure and the name of a datum, or the data as displayed in a library entry, a table row, or a database record.The term field is universal. It is sometimes used to refer to the domain or type of field, or field type.
Record
or
Row
or
Entry
Like library, record is generic term referring to an ordered set of data representing the data used by a user base for a given scope. A table is a specific term for s set of A Record is an ordered set of fields of data, treated as a unit within a database, table, or library. Record is a general database term not specific to any particular database product.
Table
or
Library
or
(sometimes Database)
A collection of records containing data.

As record is a generic term, it may be identified by a possibly unique (unspecified) means.

A record may be identified in other tables by inclusion there of this (same) key, called a secondary key.

A collection of rows containing data.

A row may be identified by a possibly unique primary key

A row may be identified in other tables by inclusion there of this (same) key.

A collection of entries containing data.

A entry may be identified by a possibly unique entry name.

An entry may be identified in other libraries by use of a Link to Entry field.

Use table outside Memento. Some people outside Memento unfortunately still use database, where we would use library.
Database One or more related tables or libraries One or more related tables One or more related libraries Use table outside Memento. Some people outside Memento unfortunately still use database, where we would use library.

The data used by a user base for a given scope

In Memento, use library. In the relational world, use table. Table is the most gernerally recognized term. (Some people outside Memento unfortunately still use database. Database One or more related tables or libraries One or more related tables One or more related libraries Use table outside Memento. Some people outside Memento unfortunately still use database, where we would use library.

The Memento Database application comprises libraries (often known outside Memento as tables), entries (often known outside Memento as rows), and fields (often known outside Memento as columns). A common generic term, recognized everywhere for either entries or rows is records.

In the Memento forum, "field" and "record" are often used and "column" and "row" is seldom used. So, it's best to stick with either Memento's "entry" (since it's their forum, after all), but when others use or seem to prefer the database industry's "record", we'll all know what is meant by that, and we can accommodate them when interacting with them, message by message in the forum.

Databases and Libraries

Likewise, within the database industry overall, "database" is used to mean the entire set of data used by a hopefully identified user or group of users to accomplish the users' personal or professional objectives, comprising libraries, entries, and fields. So, a person might use one database at home and another at work, and though many libraries will be different between libraries (like Customers at work and Groceries at home), some libraries might be used both at home and at work, often the most common and generic libraries, like People or Organizations.

When a user's objectives are so small that a single library is enough, then in that case the database is the library. However, when a user's objectives require that libraries be linked together to accomplish the objectives, now the entire set of linked libraries constitute the database. That's why, whenever we go into Edit Library > Export to create a .template file, there's an option to include linked libraries. This makes the template a database export rather than merely a library export. For more on database exports, see Export a database.

Libraries can be linked so they can work together as a database. So, each library has a structure of fields & other things (see below for what things make up its structure), and each database has a structure of libraries & links between them (see About:Database structure#Examples for an example).

The Database index, allowing quick access to Memento Database information

Yada

Introduction

Topics Overviews About
Memento Database Memento Database

Memento Wiki
Glossary
Useful links
Releases

How:Getting Started


About:Bill's mementos
About:Bill's tutorials
About:Bill's examples
Tutorial:Simple To Do List
Tutorial:Simple To Do List Enhancements
About:Color codes
CaseStudy:Designing Memento databases:Photographic equipment

Displays in the Memento mobile edition

Topics Overviews Specs Guidance
Screens & cards Libraries List screen

Library Edit screen
Entries List screen
Entry Edit card
Entry View card
File Manager card
Attached Files card
Charting data

Displays in the Memento desktop edition

Topics Overviews Specs Guidance
Windows & panes


Scripting, Calculation, & App Integration

Topics Overviews Specs Guidance
Scripting Calculation field

JavaScript field
Memento JavaScript Library
Actions
Data Sources
Triggers

Tasker Integration

Trigger Examples
How:Write scripts in JavaScript for Memento
Tips:Using JavaScript in Memento

Installation & settings

Topics Overviews Specs Guidance
Memento Settings

Import, export, synchronization, backup, & restore

Topics Overviews Specs Guidance
Backup & Restore Importing and exporting data

Formatting Templates screen

Tips:File Attachments

Cloud, platforms, & collaboration

Topics Overviews Specs Guidance
Platforms

Cloud storage and Teamwork

Cloud Library Status card

Security

Topics Overviews Specs Guidance
Privacy Policy

Library Protection

Products

Topics Overviews Specs Guidance
Memento Clients

Private Server
Team for Business

Tips:Team for Business

Jump to the index

Jump to the top