Changes between Version 53 and Version 54 of iPeerDatabaseSchema

Timestamp:

2010-10-21T20:11:11Z (14 years ago)

Author:

Serge Okon

Comment:

--

iPeerDatabaseSchema

@@ -281 +281 @@
 ||'''point_low_limit'''||integer||The minimum number of points per member, I guess, don't think it's used (?)
 ||'''point_high_limit'''||integer||The maximum number of points per member, I guess, again. (?)
+||'''record_status'''||enum(A,I)||either 'A' or 'I', representing active or inactive. Not always checked by code.
+||'''creator_id'''||integer||the ID of the ''user'' who created this course.||users
+||'''created'''||date||a date entry for this entry's creation.
+||'''updater_id'''||integer||the last ''user's'' ID who changed this record.||users
+||'''modified'''||date||the last time of modification
 == surveys ==
+Holds the Surveys. There's some confusion here, since a survey has all the info of an ''event'' in it as well. I believe both entries are created for a single survey.
+||__Column__||__Type__||__Description__||__Foreign Key to table...__||
+||'''id'''||integer||Primary_Key
+||'''course_id'''||integer||The ID of the course this Survey is for. All students in that course participate.||''courses''
+||'''user_id'''||integer||Links to ''users'' table, but why (?) Does not seem to match to creator_id, and is usually 1.||''users''
+||'''name'''||string||The name of the survey
+||'''due_date'''||date||The date this survey (and event) is due
+||'''release_date_begin'''||date||The release date for this survey (and event). Students able to access the survey after this date.
+||'''release_date_end'''||date||The final fate for this survey (and event). Students are unable to access the survey after this date.
+
 == survey_questions ==
 == survey_inputs ==