- Flat file database
A flat file database describes any of various means to encode a
data model(most commonly a table) as a plain textfile.
A flat file is a
plain textfile which usually contains one record per line. [Citation
last = Fowler
first = Glenn
year = 1994
title = cql: Flat file database query language
periodical = WTEC'94: Proceedings of the USENIX Winter 1994 Technical Conference on USENIX Winter 1994 Technical Conference
url = http://www.research.att.com/~gsf/publications/cql-1994.pdf] Within such a record, the single fields can be separated by delimiters, e.g. commas, or have a fixed length. In the latter case, padding may be needed to achieve this length. Extra formatting may be needed to avoid delimiter collision. There are no structural relationships between the records.
Typical examples of flat files are
Unix-likeoperating systems. Another example of a flat file is a name-and-address list with the fields "Name", "Address", and "Phone Number".
It is possible to write out by hand, on a sheet of paper, a list of names, addresses, and phone numbers; this is a flat file database. This can also be done with any
typewriteror word processor. Many pieces of computer software are designed to implement flat file databases.
The first uses of computing machines were implementations of simple databases.
Herman Hollerithconceived the idea that any resident of the United States could be represented by a string of exactly 80 digits and letters—name, age, and so forth, padded as needed with spaces to make everyone's name the same length, so the database fields would "line up" properly. He sold his concept, his machines, and the punched cards which both recorded and stored this data to the US Census Bureau; thus, the Census of 1890was the first ever computerized database—consisting, in essence, of thousands of boxes full of punched cards.
Throughout the years following
World War II, primitive electronic computers were run by governments and corporations; these were very often used to implement flat file databases, the most typical of which were accounting functions, such as payroll. Very quickly, though, these wealthy customers demanded more from their extremely expensive machines, which led to early relational databases. Amusingly enough, these early applications continued to use Hollerith cards, slightly modified from the original design; Hollerith's enterprise grew into computer giant IBM, which dominated the market of the time. The rigidity of the fixed-length field, 80-column punch card driven database made the early computer a target of attackClarifyme|date=March 2008, and a mystery to the common man.
In the 1980s, configurable flat-file database
computer applications were popular on DOSand the Macintosh. These programs were designed to make it easy for individuals to design and use their own databases, and were almost on par with word processorsand spreadsheets in popularity. Examples of flat-file database products were early versions of FileMakerand the shareware PC-File. Some of these offered limited relational capabilities, allowing some data to be shared between files.
Faircom's C-treeis an example of a modern enterprise-level solution, but aside from that, there are very few programs available today that would allow a novice to create and use a general-purpose flat file database. This functionality is implemented in Microsoft Works(available only for some versions of Windows) and AppleWorks, sometimes named ClarisWorks (available for both Macintosh and Windows platforms). Over time, products like Borland's Paradox, and Microsoft's Access started offering some relational capabilities, as well as built-in programming languages. Database Management Systems ( DBMS) like MySQLor Oracle generally require programmers to build applications.
Flat file databases are still used internally by many computer applications to store configuration data. Many applications allow users to store and retrieve their own information from flat files using a pre-defined set of fields. Examples are programs to manage collections of books or appointments. Some small "contact" (name-and-address) database implementations essentially use flat files.
XMLis now a popular format for storing data in plain text files, but as XML allows very complex nested data structures to be represented and contains the definition of the data, it would be incorrect to describe this type of database as conforming to the flat-file model.
"Flat file database" may be defined very narrowly, or more broadly. The narrower interpretation is correct in database theory; the broader covers the term as generally used.
Strictly, a flat file database should consist of nothing but data and delimiters. More broadly, the term refers to any database which exists in a single file in the form of rows and columns, with no relationships or links between records and fields except the table structure.
Terms used to describe different aspects of a database and its tools differ from one implementation to the next, but the concepts remain the same. FileMaker uses the term "Find", while MySQL uses the term "Query"; but the concept is the same. FileMaker "files" are equivalent to MySQL "tables", and so forth. To avoid confusing the reader, one consistent set of terms is used throughout this article.
However, the basic terms "record" and "field" are used in nearly every database implementation.
The following example illustrates the basic elements of a flat-file database. The
dataarrangement consists of a series of columns and rows organized into a tabular format. This specific example uses only one table.
The columns include: "name" (a person's name, second column); "team" (the name of an athletic team supported by the person, third column); and a numeric "unique ID", (used to uniquely identify records, first column).
Here is an example textual representation of the described data:
id name team 1 Amy Blues 2 Bob Reds 3 Chuck Blues 4 Dick Blues 5 Ethel Reds 6 Fred Blues 7 Gilly Blues 8 Hank Reds
This type of data representation is quite standard for a flat-file database, although there are some additional considerations that are not readily apparent from the text:
* Data types: each column in a database table such as the one above is ordinarily restricted to a specific
data type. Such restrictions are usually established by convention, but not formally indicated unless the data is transferred to a relational databasesystem.
* Separated columns: In the above example, individual columns are separated using whitespace characters. This is also called indentation or "fixed-width" data formatting. Another common convention is to separate columns using one or more
delimitercharacters. There are "many" different conventions for depicting data such as that above in text. (See e.g., Comma-separated values, Delimiter-separated values, Markup language, Programming language).
* Relational algebra: Each row or record in the above table meets the standard definition of a
tupleunder relational algebra(the above example depicts a series of 3-tuples). Additionally, the first row specifies the field names that are associated with the values of each row.
* Database management system: Since the formal operations possible with a text file are usually more limited than desired. The text in the above example would ordinarily represent an intermediary state of the data prior to being transferred into a
database management system.
Berkeley DB, a robust flat file database for critical applications which does ACID.
* [http://sourceforge.net/projects/textdb TextDB] , a file-based database designed to handle high loads.
SQLite, a small C library that implements a self-contained, embeddable, zero-configuration SQL database engine.
* [http://mimesis.110mb.com Mimesis] , an ffdb that uses multiple files and a heap method of storage
Wikimedia Foundation. 2010.
Look at other dictionaries:
flat file — noun a file with two flat surfaces • Hypernyms: ↑file * * * noun : a file of rectangular section about four times as wide as thick at the heel and tapering toward the point * * * flat file noun (computing) A file without hypertext links • • •… … Useful english dictionary
flat-file — flat′ file′ adj. cmp of or pertaining to a database system in which each database consists of a single file not linked to any other file • Etymology: 1980 … From formal English to slang
flat file — noun A data file containing usually one record per line. When the flat file became unmanageable, we switched to a proper database system … Wiktionary
flat-file — /flat fuyl /, adj. of or pertaining to a database system in which each database consists of a single file not linked to any other file. [1980 85] * * * … Universalium
flat-file — /flat fuyl /, adj. of or pertaining to a database system in which each database consists of a single file not linked to any other file. [1980 85] … Useful english dictionary
Database storage structures — Database tables/indexes are typically stored on hard disk in one of many forms, ordered/unordered Flat files, ISAM, Heaps, Hash buckets or B+ Trees. These have various advantages and disadvantages discussed in this topic. The most commonly used… … Wikipedia
flat-filedatabase — flat file database (flătʹfīl ) n. A database system in which each database contains only one file, which is not linked to any other file. * * * … Universalium
Database-centric architecture — or data centric architecture has several distinct meanings, generally relating to software architectures in which databases play a crucial role. Often this description is meant to contrast the design to an alternative approach. For example, the… … Wikipedia
Database model — A database model is the theoretical foundation of a database and fundamentally determines in which manner data can be stored, organized, and manipulated in a database system. It thereby defines the infrastructure offered by a particular database… … Wikipedia
File system — For library and office filing systems, see Library classification. Further information: Filing cabinet A file system (or filesystem) is a means to organize data expected to be retained after a program terminates by providing procedures to store,… … Wikipedia