View Issue Details

This bug affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
04624Bug reportsOtherpublic2010-10-13 16:22
Reportererick Assigned Toc_schmitz  
PrioritynormalSeverityminor 
Status closedResolutionfixed 
Product Version1.87+ 
Fixed in Version1.90+ 
Summary04624: Checking database integrity
Description

After deleting surveys directly in the DB from the lime_surveys table, the "Check Integrity" functionality doesn't clean all foreign references to the deleted surveys.

I found that this functionality leaves some garbage. As far as I have seen, it didn't delete records from tables lime_groups, lime_survey_languagesettings, lime_survey_rights and didn't drop the tables limetokens and limesurvey.

Steps To Reproduce

Create a new survey.
Delete it directly through in the database.
Use the Check Integrity functionality. It will clean questions and question groups, but leave the forementioned tables untouched.

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)8472
I will donate to the project if issue is resolved
Browser
Database type & versionMySQL 5
Server OS (if known)Debian Linux
Webserver software & version (if known)Apache
PHP Version5.2.6

Users monitoring this issue

There are no users monitoring this issue.

Activities

Mazi

Mazi

2010-09-24 16:05

updater   ~12904

Thibault, do you know who coded this feature?

Is it worth improving it or should we just say "don't delete surveys at the DB"? This seems to be the easier solution because I guess that when deleting a survey from the admin backend, no garbage should be left?

erick

erick

2010-09-24 16:31

reporter   ~12905

Let me add that while I think saying "don't delete surveys at the DB" is okay, I believe LimeSurvey should have a mass survey delete functionality.

This problem happened to me because I had to delete over 300 surveys.

c_schmitz

c_schmitz

2010-10-08 02:58

administrator   ~13039

Fixed in rev. 9185

c_schmitz

c_schmitz

2010-10-13 16:22

administrator   ~13130

Released in latest Plus version

Issue History

Date Modified Username Field Change
2010-09-24 14:34 erick New Issue
2010-09-24 16:04 Mazi Assigned To => lemeur
2010-09-24 16:04 Mazi Status new => assigned
2010-09-24 16:05 Mazi Note Added: 12904
2010-09-24 16:31 erick Note Added: 12905
2010-10-04 21:33 c_schmitz Assigned To lemeur => c_schmitz
2010-10-08 02:58 c_schmitz Note Added: 13039
2010-10-08 02:58 c_schmitz Status assigned => resolved
2010-10-08 02:58 c_schmitz Fixed in Version => 1.90+
2010-10-08 02:58 c_schmitz Resolution open => fixed
2010-10-13 16:22 c_schmitz Note Added: 13130
2010-10-13 16:22 c_schmitz Status resolved => closed
2010-10-25 00:21 c_schmitz Category Data Access => (No Category)