– Table structure for (Net web server) table `survey_answer` — CREATE
Thursday, June 21st, 2007– Table structure for table `survey_answer` — CREATE TABLE `survey_answer` ( `survey_id` int(11) NOT NULL, `question_id` int(11) NOT NULL, `answer` varchar(30) NOT NULL, PRIMARY KEY (`survey_id`,`question_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1; — — RELATIONS FOR TABLE `survey_answer`: — `question_id` — `survey_question` -> `id` — `survey_id` — `survey` -> `id` — — ——————————————————– — — Table structure for table `survey_question` — CREATE TABLE `survey_question` ( `id` int(11) NOT NULL, `description` varchar(40) NOT NULL, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1; — ——————————————————– Summary We improved our data structure’s implementation by assessing the responsible person for each data element and by storing this information into column comments. We then saw how to use privileges and views to improve security, how to choose the best storage engine per table, and how to benefit from foreign key constraints. Performance issues were considered, and then we were presented with the final model for the car dealer’s case study.