View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 05069 | Bug reports | Data Entry (non public) | public | 2011-03-31 18:24 | 2011-03-31 21:55 |
| Reporter | tacman1123 | Assigned To | c_schmitz | ||
| Priority | normal | Severity | minor | ||
| Status | closed | Resolution | won't fix | ||
| Product Version | 1.91RC5 | ||||
| Summary | 05069: Checkbox answer field names need separators | ||||
| Description | In the survey_xxxx table, where responses are stored, the field names of subquestions are now in the form <survey>X<section>X<qid><subquestionid>. I could have sworn that this format used to be in the normal format, where qid was the question id of the subquestion (since we have a unique question id for it, I don't know why it needs to reference the parent id and then have an offset). Since I'm trying to use the database outside of the Lime core code, this is a real pain, but I think it's a problem with lime as well. Suppose Question 1 is 2-answer multiple choice (aka checkboxes), then the field name is going to be (assuming survey 7 section 1) 7X1X11 Then suppose question 11 is a radio answer (a single answer), it's field name would also be 7X1X11 Perhaps I'm missing something here, but it seems to be very problematic that there's no separator between the question id and the offset in order to uniquely identify the subquestion. I think it should either be the question id of the subquestion, OR have a separator, maybe another 'X'. | ||||
| Additional Information | Perhaps in V2 the answers can be stored differently. The section id seems unnecessary, as is the survey id, as each question is already uniquely defined globally, and certainly within the survey itself. It'd be easier to integrate the lime data if the field names (1) didn't start with a number and (2) used the question codes / answer codes when we have them. So the fields could be school, or in the case of multiple answers, music.guitar, music.drums, etc., and then music._OTHER I realize that's a major change to the code, but the subquestion issue I've reported seems like a bigger one with potential conflicts. | ||||
| Tags | No tags attached. | ||||
| Bug heat | 6 | ||||
| Complete LimeSurvey version number (& build) | 9909 | ||||
| I will donate to the project if issue is resolved | Yes | ||||
| Browser | |||||
| Database type & version | MySQL 5 | ||||
| Server OS (if known) | Linux | ||||
| Webserver software & version (if known) | Apache | ||||
| PHP Version | 5.3 | ||||
| Git branch / Pull Request URL | |||||
|
Whoops, I meant to say the field names of subquestions are now in the form <survey>X<section>X<qid><subquestion_index>. (not subquestion_id) |
|
|
This is not a bug and the issue is taken care of. On survey activation LimeSurvey checks for collisions like that. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2011-03-31 18:24 | tacman1123 | New Issue | |
| 2011-03-31 18:43 | tacman1123 | Note Added: 14624 | |
| 2011-03-31 18:44 | tacman1123 | Issue Monitored: tacman1123 | |
| 2011-03-31 21:55 | c_schmitz | Note Added: 14625 | |
| 2011-03-31 21:55 | c_schmitz | Status | new => closed |
| 2011-03-31 21:55 | c_schmitz | Assigned To | => c_schmitz |
| 2011-03-31 21:55 | c_schmitz | Resolution | open => won't fix |