Diffstat (limited to 'development/pim/dbpaper/intro.tex') (more/less context) (ignore whitespace changes)
-rw-r--r-- | development/pim/dbpaper/intro.tex | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/development/pim/dbpaper/intro.tex b/development/pim/dbpaper/intro.tex index c456333..fd790d7 100644 --- a/development/pim/dbpaper/intro.tex +++ b/development/pim/dbpaper/intro.tex | |||
@@ -9,23 +9,23 @@ This draft paper describes the database layout of the Opie PIM applications. | |||
9 | Design goal is a fast and extendable layout on a sql database to support cross referencing. | 9 | Design goal is a fast and extendable layout on a sql database to support cross referencing. |
10 | 10 | ||
11 | 11 | ||
12 | \subsection{Copyright} | 12 | \subsection{Copyright} |
13 | 13 | ||
14 | Copyright notice | 14 | Copyright notice |
15 | \copyright 2002, Maximilian Rei{\ss} \& Stefan Eilers \& Holger Freyther | 15 | \copyright 2002-2004, Maximilian Rei{\ss} \& Stefan Eilers \& Holger Freyther |
16 | 16 | ||
17 | \pagebreak | 17 | \pagebreak |
18 | \section{Relations} | 18 | \section{Relations} |
19 | \subsection{About Cross Referencing and Horizontal Data Storage} | 19 | \subsection{About Cross Referencing and Horizontal Data Storage} |
20 | Before you read on, it may be helpful to get some information about the solution of ``horizontal'' data storage into the tables and cross referencing. | 20 | Before you read on, it may be helpful to get some information about the solution of ``horizontal'' data storage into the tables and cross referencing. |
21 | Some of the tables are just using 5 attributes: | 21 | Some of the tables are just using 5 attributes: |
22 | \begin{enumerate} | 22 | \begin{enumerate} |
23 | \item UID: This countains an unique ID for the complete entry. An entry may consist of multiple | 23 | \item UID: This countains an unique ID for the complete entry. An entry may consist of multiple |
24 | rows, seperated by ID. | 24 | rows, seperated by ID. |
25 | \item ID: This defines a number to seperate the rows of an entry. UID + ID must be unique for every entry. | 25 | \item ID: This defines a number to seperate the rows of an entry. UID + ID must be unique for every entry (primary key). |
26 | \item Type: Describes the type of this entry. | 26 | \item Type: Describes the type of this entry. |
27 | \item Priority: For instance: Your default email-address will get the priority 1 and the other 2.. . 0 means ``not defined''. | 27 | \item Priority: For instance: Your default email-address will get the priority 1 and the other 2.. . 0 means ``not defined''. |
28 | \item Value: The data which was described by ``Type'' is stored here. | 28 | \item Value: The data which was described by ``Type'' is stored here. |
29 | \end{enumerate} | 29 | \end{enumerate} |
30 | 30 | ||
31 | These kinds of tables are very flexible in what they may contain, due to the fact that the ``Type'' may be without any constraint. Therefore it is perfectly for storing personal information, which may change in the future, or should be increased. | 31 | These kinds of tables are very flexible in what they may contain, due to the fact that the ``Type'' may be without any constraint. Therefore it is perfectly for storing personal information, which may change in the future, or should be increased. |