1. Tables versus relations

2. Comparisons
    Hierarchical databases  Spreadsheets 

3. See also

4. References

A table is a collection of related data held in a table format within a database. It consists of columns, and rows.

In relational databases, and flat file databases, a table is a set of data elements (values) using a model of vertical columns (identifiable by name) and horizontal rows, the cell being the unit where a row and column intersect.^[1] A table has a specified number of columns, but can have any number of rows.^[2] Each row is identified by one or more values appearing in a particular column subset. A specific choice of columns which uniquely identify rows is called the primary key.

"Table" is another term for "relation"; although there is the difference in that a table is usually a multiset (bag) of rows where a relation is a set and does not allow duplicates. Besides the actual data rows, tables generally have associated with them some metadata, such as constraints on the table or on the values within particular columns.{{Dubious|reason=Metadata is "data about data". A check constraint doesn't have such property|date=September 2012}}

The data in a table does not have to be physically stored in the database. Views also function as relational tables, but their data are calculated at query time. External tables (in Informix^[3]

or Oracle,^[4][5]

for example) can also be thought of as views.

Tables versus relations

In terms of the relational model of databases, a table can be considered a convenient representation of a relation, but the two are not strictly equivalent. For instance, a SQL table can potentially contain duplicate rows, whereas a true relation cannot contain duplicate tuples. Similarly, representation as a table implies a particular ordering to the rows and columns, whereas a relation is explicitly unordered. However, the database system does not guarantee any ordering of the rows unless an ORDER BY clause is specified in the SELECT statement that queries the table.

An equally valid representation of a relation is as an n-dimensional chart, where n is the number of attributes (a table's columns). For example, a relation with two attributes and three values can be represented as a table with two columns and three rows, or as a two-dimensional graph with three points. The table and graph representations are only equivalent if the ordering of rows is not significant, and the table has no duplicate rows.

Comparisons

Hierarchical databases

In non-relational systems, hierarchical databases, the distant counterpart of a table is a structured file, representing the rows of a table in each row of the file and each column in a row. This structure implies that a row can have repeating information, generally in the child data segments. Data are stored in sequence of physical records.

Spreadsheets

Unlike a spreadsheet, the datatype of a column is ordinarily defined by the schema describing the table. Some SQL systems, such as SQLite, are less strict about column datatype definitions.

See also

• Relation (database)
• Row (database)
• Column (database)
• Virtual column
• Table (information)

References

• 2013–14 Luge World Cup
• 2013–14 Luton Town F.C. season
• 2013–14 Luxembourg Cup
• 2013–14 Luxembourg National Division
• 2013–14 LV Cup
• 2013–14 Maccabi Haifa F.C. season
• 2013–14 Maccabi Tel Aviv F.C. season
• 2013–14 Macedonian Cup
• 2013–14 Macedonian First Football League
• 2013–14 Macedonian Football Cup
• 2013–14 Macedonian Second Football League
• 2013–14 Macedonian Third Football League
• 2013–14 Macedonian Vtora Liga
• 2013–14 Magyar Kupa
• 2013–14 Maine Black Bears men's basketball team
• 2013–14 Maio Island League
• 2013–14 Major Indoor Soccer League season
• 2013–14 Malaga CF season
• 2013–14 Malmo Redhawks season
• 2013–14 Malmö Redhawks season
• 2013–14 Maltese FA Trophy
• 2013–14 Maltese First Division
• 2013–14 Maltese Premier League
• 2013–14 Maltese Second Division
• 2013–14 Manchester City F.C. season