View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
04305Bug reportsOtherpublic2010-05-04 14:152010-06-29 20:35
ReporterGrupBlau Assigned Toc_schmitz  
PriorityhighSeverityminor 
Status closedResolutionunable to reproduce 
Product Version1.87+ 
Summary04305: Fails to drop old token table on integrity check
Description

On URL: limesurvey/admin/admin.php?action=checkintegrity
I get:
Couldn't drop table lime_old_tokens_49698_20091211125706_tid_seq (DROP TABLE lime_old_tokens_49698_20091211125706_tid_seq)
ERROR: cannot drop table lime_old_tokens_49698_20091211125706_tid_seq because other objects depend on it HINT: Use DROP ... CASCADE to drop the dependent objects too.

Additional Information

It is an upgrade from 1.86 to 1.87. I did not try to drop tables on 1.86.

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)8518
I will donate to the project if issue is resolved
Browser
Database type & versionPostgreSQL 8.3
Server OS (if known)Linux Debian Lenny
Webserver software & version (if known)Apache2 2.2.9
PHP Version5.2.6

Users monitoring this issue

There are no users monitoring this issue.

Activities

machaven

machaven

2010-05-05 08:14

reporter   ~11706

Thanks for the bug report i will have a look.
machaven

machaven

2010-05-18 12:07

reporter   ~11844

Adding this note, do not have a setup to test yet.

The sequence seems to belong to the old table and should be set none if tokens are dropped completely or to the new table column if a new tokens table is created.

ALTER SEQUENCE OWNED BY

OWNED BY table.column
OWNED BY NONE

The OWNED BY option causes the sequence to be associated with a specific table column, such that if that column (or its whole table) is dropped, the sequence will be automatically dropped as well. If specified, this association replaces any previously specified association for the sequence. The specified table must have the same owner and be in the same schema as the sequence. Specifying OWNED BY NONE removes any existing association, making the sequence "free-standing".
c_schmitz

c_schmitz

2010-06-03 16:21

administrator   ~12110

I checked this on 1.90 and and Postgres 8.4 and found no problem.
GrupBLau, can you please test-install 1.90 and see if it is resolved there?
c_schmitz

c_schmitz

2010-06-16 22:14

administrator   ~12231

GrupBlau?
c_schmitz

c_schmitz

2010-06-29 20:35

administrator   ~12310

Closing issue due to missing feedback.

Issue History

Date Modified Username Field Change
2010-05-04 14:15 GrupBlau New Issue
2010-05-05 08:14 machaven Note Added: 11706
2010-05-05 08:14 machaven Assigned To => machaven
2010-05-05 08:14 machaven Status new => acknowledged
2010-05-05 08:15 machaven Status acknowledged => assigned
2010-05-18 12:07 machaven Note Added: 11844
2010-06-01 21:37 machaven Assigned To machaven => c_schmitz
2010-06-03 16:21 c_schmitz Note Added: 12110
2010-06-03 16:21 c_schmitz Status assigned => feedback
2010-06-16 22:14 c_schmitz Note Added: 12231
2010-06-17 23:32 c_schmitz Priority normal => high
2010-06-29 20:35 c_schmitz Note Added: 12310
2010-06-29 20:35 c_schmitz Status feedback => closed
2010-06-29 20:35 c_schmitz Resolution open => unable to reproduce