- Quiz module does not support Drupal DB extensions
- There is a table just called “multichoice”.. this should probably be called quiz_question_type_multichoice or something like that, to keep with current naming conventions
- Addition of “time_limit” field to quiz table
- Addition of include, exclude, and feedback fields to quiz_question table
- What is the “status” field in quiz_questions?
- Create question_revision_queue table

Comments

webchick’s picture

Status: Active » Fixed

- Quiz module does not support Drupal DB extensions

Sorry, no idea what this is referring to. :P

- There is a table just called “multichoice”.. this should probably be called quiz_question_type_multichoice or something like that, to keep with current naming conventions

Robert actually said to leave this alone for now, so...

- Addition of “time_limit” field to quiz table

Added "time_limit", as an INTEGER field. This will store a time limit in seconds, or 0 for unlimited.

- Addition of include, exclude, and feedback fields to quiz_question table

Nope. Got this one wrong. Including/Excluding happens based on the status field (see below) and feedback is stored in the individual question types' tables.

- What is the “status” field in quiz_questions?

This was me being stupid again. ;) Status indicates whether the question is:

0 - Random (may appear in the quiz or not)
1 - Always
2 - Never

...included in the quiz.

- Create question_revision_queue table

Done (named it quiz_question_revision_queue, per naming guidelines (though ugh, what a mouthful ;P).

For now, I've gone with the first option listed here: http://www.webs4.com/node/28; It seems more sensible to try and utilize the existing node revision API than to 're-invent the wheel.' However, when it comes time to implement this functionality, if too many difficulties come up, this could be swapped to the other option, where revisions themselves are stored in this table.

webchick’s picture

Assigned: Unassigned » webchick

- Quiz module does not support Drupal DB extensions

Actually, Rob clarified this, and was referring to the fact that calls to the tables are "hard-coded" to be quiz_whatever, which is no good if the site uses prefixes on their tables (drupal_).

Changed the tablename in all db_query()s to {tablename} to allow Drupal to handle this.

Anonymous’s picture

Anonymous’s picture

Anonymous’s picture

Anonymous’s picture

Anonymous’s picture

Anonymous’s picture

Status: Fixed » Closed (fixed)