- Timestamp:
- 12/23/11 16:39:06 (13 years ago)
- Location:
- Doc
- Files:
-
- 3 edited
-
Backend/DBInterface.pdf (modified) (previous)
-
Backend/DBInterface.tex (modified) (2 diffs)
-
Diagrams/ResearchTool_withGameResults.vsd (modified) (previous)
Legend:
- Unmodified
- Added
- Removed
-
Doc/Backend/DBInterface.tex
r189 r196 151 151 way around this, so here is a complete overview of arguments per type. \\ 152 152 \begin{tabular}{| l | c | c | l |} \hline 153 \textbf{Type} & \textbf{Argument name} & \textbf{Argument type}& \textbf{Extra notes} \\ \hline \hline154 \multirow{3}{*}{Answer} & uid & String & \\153 \textbf{Type} & \textbf{Argument name} & \textbf{Argument type} & \textbf{Extra notes} \\ \hline \hline 154 \multirow{3}{*}{Answer} & uid & String & \\ 155 155 & question & String & UID of the question \\ 156 & values & Array of Strings & \\ \hline \hline157 \multirow{4}{*}{AnswerSet} & uid & String & \\156 & values & Array of Strings & \\ \hline \hline 157 \multirow{4}{*}{AnswerSet} & uid & String & \\ 158 158 & survey & String & UID of the Survey \\ 159 159 & respondent & String & UID of the Respondent \\ 160 & answers & Array of Strings & UIDs of the Answers \\ \hline \hline161 \multirow{4}{*}{Application} & uid & String & \\162 & title & String & \\ 163 & description & String & \\164 & style 165 \multirow{5}{*}{Question} & code& String & \\166 & title & String & \\ 167 & type 168 & description & String & \\160 & answers & Array of Strings & UIDs of the Answers \\ \hline \hline 161 \multirow{4}{*}{Application} & uid & String & \\ 162 & title & String & \\ 163 & description & String & \\ 164 & style & String & \\ \hline \hline 165 \multirow{5}{*}{Question} & code & String & \\ 166 & title & String & \\ 167 & type & String & \\ 168 & description & String & \\ 169 169 & category & String & \\ 170 & definedanswers & Array of Strings& String values of possible answers \\ \hline \hline171 \multirow{3}{*}{Respondent/User} & uid & String & \\172 & name 170 & definedanswers & Array of Strings & String values of possible answers \\ \hline \hline 171 \multirow{3}{*}{Respondent/User} & uid & String & \\ 172 & name & String & \\ 173 173 & password & String & Use hashes to store passwords \\ \hline \hline 174 \multirow{ 6}{*}{Session}& uid & String & \\174 \multirow{7}{*}{Session} & uid & String & \\ 175 175 & title & String & \\ 176 176 & creator & String & UID of the User \\ 177 & datetime & String & Unix Timestamp. No way to search on intervals (yet). \\ 178 & applications & Array of Strings & UIDs of the Applications \\ 179 & surveys & Array of Strings & UIDs of the Surveys \\ 180 & answersets & Array of Strings & UIDs of the AnswerSets \\ \hline \hline 181 \multirow{4}{*}{Survey} & uid & String & \\ 182 & title & String & \\ 183 & description & String & \\ 177 & creationdate & String & Unix Timestamp. No way to search on intervals (yet). \\ 178 & applications & Array of Strings & UIDs of the Applications \\ 179 & surveys & Array of Strings & UIDs of the Surveys \\ 180 & answersets & Array of Strings & UIDs of the AnswerSets \\ \hline \hline 181 \multirow{9}{*}{SessionInstance} & uid & String & \\ 182 & title & String & \\ 183 & location & String & \\ 184 & facilitator & String & UID of the user that facilitated the session \\ 185 & startime & String & Unix Timestamp. No way to search on intervals (yet). \\ 186 & endtime & String & Unix Timestamp. No way to search on intervals (yet). \\ 187 & notes & Array of Strings & \\ 188 & session & String & UID of the Session this Instance refers to. \\ 189 & resultset & String & UID of the ResultSet this Instance has. \\ \hline \hline 190 \multirow{4}{*}{Survey} & uid & String & \\ 191 & title & String & \\ 192 & description & String & \\ 184 193 & creator & String & UID of the user that created this survey \\ 185 & questions & Array of Strings & UIDs of the Questions \\ \hline \hline194 & questions & Array of Strings & UIDs of the Questions \\ \hline \hline 186 195 \end{tabular} \\ 187 196 … … 223 232 This goes in two parts. Firstly, the database now assumes that given an entry, all the fields for its type are there and 224 233 filled in. This is unwanted since it can cause issues with backwards compatability of certain .rdf files. Secondly, it 225 assumes that fields containing a UID to a different entry actually point to a valid entry. For instance, a Survey querywill226 try to get a User object as its creator value from the database as well, assuming it exists. It will breakif this user object234 assumes that fields containing a UID to a different entry actually point to a valid entry. For instance, a Survey evaluation will 235 try to get a User object as its creator value from the database as well, assuming it exists. It will return false if this user object 227 236 does not exist. 228 237
Note: See TracChangeset
for help on using the changeset viewer.
