summaryrefslogtreecommitdiff
path: root/development/pim/dbpaper/intro.tex
Unidiff
Diffstat (limited to 'development/pim/dbpaper/intro.tex') (more/less context) (ignore whitespace changes)
-rw-r--r--development/pim/dbpaper/intro.tex63
1 files changed, 29 insertions, 34 deletions
diff --git a/development/pim/dbpaper/intro.tex b/development/pim/dbpaper/intro.tex
index 0a26b90..c456333 100644
--- a/development/pim/dbpaper/intro.tex
+++ b/development/pim/dbpaper/intro.tex
@@ -15,23 +15,24 @@ Copyright notice
15\copyright 2002, Maximilian Rei{\ss} \& Stefan Eilers \& Holger Freyther 15\copyright 2002, 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}
20Before you read on, it may be helpful to get some information about the solution of ``horizontal'' data storage into the tables and cross referencing. 20Before you read on, it may be helpful to get some information about the solution of ``horizontal'' data storage into the tables and cross referencing.
21Some of the tables are just using 4 attributes: 21Some 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. 23\item UID: This countains an unique ID for the complete entry. An entry may consist of multiple
24\item ID: This defines a number to seperate the rows of an entry. 24rows, 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 Type: Describes the type of this entry. 26\item Type: Describes the type of this entry.
26\item Value: And the data which was described by ``Type'' is stored here. 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.
27\end{enumerate} 29\end{enumerate}
28 30
29These 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. The other advantage is the fact that these tables are automatically convertable into XML: 31These 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.
30The ``Type'' has just to be converted into an ``attribute'' in a XML-tag. Thats all, and that will work for all future Types ! 32\\
31
32Let's see how such an entry may look like for the table ``ADDRESSBOOK'': 33Let's see how such an entry may look like for the table ``ADDRESSBOOK'':
33 34
34\begin{tabular}[ht]{|l|l|l|l|} 35\begin{tabular}[ht]{|l|l|l|l|}
35\hline 36\hline
36\underline{UID} & \underline{ID} & Type & Value\\ 37\underline{UID} & \underline{ID} & Type & Value\\
37\hline 38\hline
@@ -41,72 +42,66 @@ Let's see how such an entry may look like for the table ``ADDRESSBOOK'':
41\hline 42\hline
42 1231& 02& LastName& Eilers\\ 43 1231& 02& LastName& Eilers\\
43\hline 44\hline
44\end{tabular} 45\end{tabular}
45\\ 46\\
46\\ 47\\
47We need some additional information about this entry, which is stored into the table ``PERSONAL\_DATA\_CONTACT'': 48We need some additional information about this entry, which is stored into the table ``PERSONAL\_DATA'':
48\\ 49\\
49\\ 50\\
50\begin{tabular}[ht]{|l|l|l|l|} 51\begin{tabular}[ht]{|l|l|l|l|l|}
51\hline 52\hline
52\underline{UID} & \underline{ID} & Type & Value\\ 53\underline{UID} & \underline{ID} & Type & Priority & Value\\
53\hline 54\hline
54 2345& 00& Email& eilers@sra.uni-hannover.de, eilers.stefan@epost.de\\ 55 2345& 00& Email& 1& eilers.stefan@epost.de\\
55\hline 56\hline
56 2345& 01& DefaultEmail& eilers@sra.uni-hannover.de\\ 57 2345& 01& Email& 2& eilers@sra.uni-hannover.de\\
57\hline 58\hline
58 2345& 02& HomeWebPage& www.sra.uni-hannover.de/$\sim$eilers/\\ 59 2345& 02& WebPage& 1& www.sra.uni-hannover.de/$\sim$eilers/\\
59\hline 60\hline
60\end{tabular} 61\end{tabular}
61\\ 62\\
62\\ 63\\
63The last question is: How to get these information together? This is the job of the cross-referencing-table\footnote{We expecting that the table ``PERSONAL\_DATA\_CONTACT'' was registered in the table ``TABLEID'' as table ``03''!}: 64The last question is: How to get these information together? This is the job of the cross-referencing-table\footnote{We expecting that the table ``PERSONAL\_DATA'' was registered in the table ``TABLEID'' as table ``03''and ADDRESSBOOK with ``01''!}:
64\\ 65\\
65\\ 66\\
66\begin{tabular}[ht]{|l|l|l|l|l|l|} 67\begin{tabular}[ht]{|l|l|l|l|l|l|}
67\hline 68\hline
68\underline{TID1} & \underline{UID1} & \underline{Type1} & \underline{TID2} & \underline{UID2} & \underline{Type2} \\ 69\underline{TID1} & \underline{UID1} & \underline{ID1} & \underline{TID2} & \underline{UID2} & \underline{ID2} \\
69\hline 70\hline
70 01& 1231& & 03& 2345&\\ 71 01& 1231& (NULL) & 03& 2345& (NULL) \\
71\hline 72\hline
72\end{tabular} 73\end{tabular}
73\\ 74\\
74\\ 75\\
75Type was left empty, due to the fact that we wanted to link the complete entry and not some rows of the entry. 76ID was left empty, due to the fact that we wanted to link the complete entry and not some rows of the entry.
76\\ 77\\
77In some cases, it may be useful to reference in a much more smaller granularity than complete entries. What should we do, if we want to store the children of a person ? 78In some cases, it may be useful to reference in a much more smaller granularity than complete entries. What should we do, if we want to store the children of a person ?
78The easiest way is to store the children into the table ``PERSONAL\_DATA'':\footnote{We expecting that the table ``PERSONAL\_DATA'' was registered in the table ``TABLEID'' as table ``05''!}\\ 79The easiest way is to store the children into the table ``PERSONAL\_DATA'':\footnote{We remember that the table ``PERSONAL\_DATA'' was registered in the table ``TABLEID'' as table ``03''!}, too.\\
79\\ 80\\
80\begin{tabular}[ht]{|l|l|l|l|} 81\begin{tabular}[ht]{|l|l|l|l|l|}
81\hline 82\hline
82\underline{UID} & \underline{ID} & Type & Value\\ 83\underline{UID} & \underline{ID} & Type & Priority & Value\\
83\hline 84\hline
84 2344& 11& Children& Amaly, Karl, Clarissa\\ 85 2345& 11& Child & 0 & Amaly \\
85\hline 86\hline
86\end{tabular}\\ 87 2345& 12& Child & 0 & Karl \\
87\\
88and reference it again with the table ``ADDRESSBOOK'':\\
89\\
90\begin{tabular}[ht]{|l|l|l|l|l|l|}
91\hline 88\hline
92\underline{TID1} & \underline{UID1} & \underline{Type1} & \underline{TID2} & \underline{UID2} & \underline{Type2} \\ 89 2345& 13& Child & 0 & Clarissa\\
93\hline 90\hline
94 01& 1231& & 05& 2344&\\ 91\end{tabular}\\
95\hline
96\end{tabular}
97\\
98\\ 92\\
93
99But what happens if you want to store additional information about the children, as there mobile phone numbers, etc? 94But what happens if you want to store additional information about the children, as there mobile phone numbers, etc?
100 95
101In this case we need an entry in addressbook and a reference to this entry. Lets expect ``Amaly'' was stored in the table ``ADDRESSBOOK'' with UID 9213 and Karl with UID 7654. A cross-reference will look like this:\\ 96In this case we need an entry in addressbook and a reference to this entry. Lets expect ``Amaly'' was stored in the table ``ADDRESSBOOK'' with UID 9213 and Karl with UID 7654. A cross-reference will look like this:\\
102\\ 97\\
103\begin{tabular}[ht]{|l|l|l|l|l|l|} 98\begin{tabular}[ht]{|l|l|l|l|l|l|}
104\hline 99\hline
105\underline{TID1} & \underline{UID1} & \underline{Type1} & \underline{TID2} & \underline{UID2} & \underline{Type2} \\ 100\underline{TID1} & \underline{UID1} & \underline{ID1} & \underline{TID2} & \underline{UID2} & \underline{ID2} \\
106\hline 101\hline
107 05& 2344& Children& 01& 9213& \\ 102 03& 2345& 11& 01& 9213& (NULL) \\
108\hline 103\hline
109 05& 2344& Children& 01& 7654& \\ 104 03& 2345& 12& 01& 7654& (NULL) \\
110\hline 105\hline
111\end{tabular} 106\end{tabular}
112\\ 107\\