Changeset 179 for Doc/Backend/DBInterface.tex
- Timestamp:
- 12/09/11 10:39:10 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
Doc/Backend/DBInterface.tex
r172 r179 207 207 208 208 \section{Future Work}\label{futurework} 209 //TODO 209 \subsection{Adhere to Open-Closed Principle} 210 At the moment, \textit{the DatabaseInterface.php} class violates the Open-Closed principle. Every new connector, 211 four lines need to be added in this class. This is unwanted if new RDF datatypes are added. The same holds for 212 the method createArguments in this class: extra cases have to be added if more types of arguments become possible. 213 Adhering to the Open-Closed principle will allow for easier extention and maintenance of the database-related classes. 214 215 \subsection{Deal with invalid or missing values} 216 This goes in two parts. Firstly, the database now assumes that given an entry, all the fields for its type are there and 217 filled in. This is unwanted since it can cause issues with backwards compatability of certain .rdf files. Secondly, it 218 assumes that fields containing a UID to a different entry actually point to a valid entry. For instance, a Survey query will 219 try to get a User object as its creator value from the database as well, assuming it exists. It will break if this user object 220 does not exist. 210 221 211 222 \appendix
Note: See TracChangeset
for help on using the changeset viewer.