Welcome, Guest
Username: Password: Remember me

TOPIC: upgrade-postgres.php messed up in limesurvey192plus-build120314.zip

upgrade-postgres.php messed up in limesurvey192plus-build120314.​zip 2 years 1 month ago #76755

Hi,

I'm guessing "bug" but not certain how best to report it. It appears update-postgres.php wasn't written for postgresql: Integer values with string defaults, an "auto_increment" where a "serial" should be, and a primary key that appears to have nothing to do with the table in which it is specified. I just attempted to upgrade and got the following back [which I re-wrapped]:
The LimeSurvey database is being upgraded (2012-03-16 13:24:48)
.Please be patient...
 
. . .
SQL command failed: ALTER TABLE user ADD participant_panel integer NOT
NULL default '0' Reason: ERROR: syntax error at or near "user" LINE 1:
ALTER TABLE user ADD participant_panel integer NOT NULL defa... ^
. . . .
SQL command failed: CREATE TABLE participant_attribute_values (
attribute_id integer NOT NULL, value_id integer NOT NULL
AUTO_INCREMENT, value character varying( 20 ) NOT NULL, PRIMARY KEY
(value_id) ) Reason: ERROR: syntax error at or near "AUTO_INCREMENT"
LINE 3: value_id integer NOT NULL AUTO_INCREMENT, ^
 
SQL command failed: CREATE TABLE participant_shares ( participant_id
character varying( 50 ) NOT NULL, shared_uid integer NOT NULL,
date_added date NOT NULL, can_edit character varying( 5 ) NOT NULL,
PRIMARY KEY (lang,attribute_id) ) Reason: ERROR: column "lang" named
in key does not exist
. . . . . . . . . . . . . . . . . .
 
Database update finished (2012-03-16 13:24:49)
Database has been successfully upgraded to version 155

Was it REALLY a successful upgrade?
The administrator has disabled public write access.

Aw: upgrade-postgres.php messed up in limesurvey192plus-build120314.​zip 2 years 3 weeks ago #76958

  • Steve
  • Steve's Avatar
  • OFFLINE
  • LimeSurvey Team
  • Posts: 494
  • Thank you received: 46
  • Karma: 17
Hello,

Please test if the problem still exists at the latest release. If so please open a ticket at the bugtracker and...
  1. Give as much information as possible
  2. Attach your survey. You can mark your ticket "private" so that only the developers will be able to take a look at it.
  3. Provide step-by-step instructions how to reproduce the problem.
  4. If possible/helpful please provide screenshots

Afterwards please post the link to the bugtracker so we can follow the progress.

Thanks!
Mit freundlichen Grüßen/Best regards,

Stefan Gohlke
LimeSurvey Team
The administrator has disabled public write access.
Moderators: ITEd
Time to create page: 0.146 seconds
Donation Image