View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
06090 | Bug reports | Other | public | 2012-05-13 14:33 | 2012-05-28 15:12 |
Reporter | mars99 | Assigned To | c_schmitz | ||
Priority | high | Severity | partial_block | ||
Status | closed | Resolution | fixed | ||
Product Version | 2.00RC1 | ||||
Fixed in Version | 2.00RC2 | ||||
Summary | 06090: Activating a survey ends with a database (SQL) error on PostgreSQL | ||||
Description | Activating a survey ends with an error on PostgreSQL while copying the questionaire to it's own table. Here the original error message: [..] Database error!! | ||||
Steps To Reproduce | I created a survey of 10 questions (using Array, multiple choice,...) with lots of subquestions which took some time because I had to work around Bug 06088 1.) Login in to Limesurvey Admin backend | ||||
Tags | No tags attached. | ||||
Bug heat | 2 | ||||
Complete LimeSurvey version number (& build) | 120510 | ||||
I will donate to the project if issue is resolved | No | ||||
Browser | |||||
Database type & version | PostgreSQL 9.1.3 | ||||
Server OS (if known) | Ubuntu 12.04 LTS (ARM) | ||||
Webserver software & version (if known) | lighttpd/1.4.28 | ||||
PHP Version | PHP5 (5.3.10-1*) | ||||
Fix committed to Yii branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=8490 |
|
Version 2.00RC2 released. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2012-05-13 14:33 | mars99 | New Issue | |
2012-05-16 15:48 | c_schmitz | Assigned To | => c_schmitz |
2012-05-16 15:48 | c_schmitz | Status | new => assigned |
2012-05-16 15:48 | c_schmitz | Changeset attached | => LimeSurvey Yii ca586fd4 |
2012-05-16 15:48 | c_schmitz | Note Added: 18781 | |
2012-05-16 15:48 | c_schmitz | Resolution | open => fixed |
2012-05-16 15:48 | c_schmitz | Status | assigned => resolved |
2012-05-16 15:48 | c_schmitz | Fixed in Version | => 2.00RC2 |
2012-05-28 15:12 | c_schmitz | Note Added: 18958 | |
2012-05-28 15:12 | c_schmitz | Status | resolved => closed |