View Issue Details

This bug affects 1 person(s).
 4
IDProjectCategoryView StatusLast Update
06416Bug reportsImport/Exportpublic2012-08-20 12:48
ReporterMazi Assigned Toc_schmitz  
PrioritynormalSeverityminor 
Status closedResolutionfixed 
Product Version1.92+ 
Target Version2.00RC9Fixed in Version2.00RC9 
Summary06416: MySQL DB backup feature doesn't copy indexes
Description

When creating a DB backup using the "Backup entire database" feature (MySQL only), indexes are not included at the backup so once you restore the backup, your system might run slower than before.

Furthermore the current auto-increment count is not kept which might mean that the system will start with the lowest available value.

Steps To Reproduce

Run the "Backup entire database" feature and compare to a fresh Limesurvey install.

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)120801
I will donate to the project if issue is resolvedNo
BrowserFirefox 12
Database type & versionMySQL 5
Server OS (if known)Win 7
Webserver software & version (if known)Apache 2.2
PHP Version5.3.1

Users monitoring this issue

There are no users monitoring this issue.

Activities

c_schmitz

c_schmitz

2012-08-05 18:08

administrator   ~20203

This is already in 2.0.

c_schmitz

c_schmitz

2012-08-16 10:23

administrator   ~20477

Version 2.00 RC 9 released.

Mazi

Mazi

2012-08-20 11:38

updater   ~20545

Carsten, are you sure that the indexes are already added by the dump feature of Limesurveyc 2?

IRC log:
[11:14] Mazi: c_schmitz, ajs: At Limesurvey 2, where can I find the file which holds the code to generate the SQL file for the "Backup entire database" feature?
[11:15] ajs: application/controllers/admin/dumpdb.php
[11:17] ajs: Mazi: ^
[11:18] Mazi: thanks, ajs
[11:34] Mazi: ajs, maybe you can help with this question as well, related to bug http://bugs.limesurvey.org/view.php?id=6416
[11:34] Mazi: -> which part of the code at application/controllers/admin/dumpdb.php is responsible for creating the indexes?
[11:36] ajs: Mazi: as far as I can tell there is no code related to creating indexes
[11:37] ajs: That seems to be what the bug report is about
[11:37] Mazi: that was my impression as well
[11:37] Mazi: I'll reopen the bug then

Furthermore, I think it would be very useful to fix this for the last 1.92 release as well!

c_schmitz

c_schmitz

2012-08-20 12:48

administrator   ~20546

Last edited: 2012-08-20 12:49

Yes, I am sure. It is not a critical issue so I won't fix this for 1.92 anymore. Feel free to have a go at it if it is so important for you.

Issue History

Date Modified Username Field Change
2012-08-01 14:46 Mazi New Issue
2012-08-01 14:46 Mazi Status new => assigned
2012-08-01 14:46 Mazi Assigned To => c_schmitz
2012-08-05 18:08 c_schmitz Note Added: 20203
2012-08-05 18:08 c_schmitz Status assigned => resolved
2012-08-05 18:08 c_schmitz Fixed in Version => 2.00+
2012-08-05 18:08 c_schmitz Resolution open => fixed
2012-08-12 15:32 c_schmitz Fixed in Version 2.00+ => 2.00RC9
2012-08-15 00:22 c_schmitz Target Version 2.00+ => 2.00RC9
2012-08-16 10:23 c_schmitz Note Added: 20477
2012-08-16 10:23 c_schmitz Status resolved => closed
2012-08-20 11:38 Mazi Note Added: 20545
2012-08-20 11:38 Mazi Status closed => feedback
2012-08-20 11:38 Mazi Resolution fixed => reopened
2012-08-20 11:38 Mazi Status feedback => assigned
2012-08-20 12:48 c_schmitz Note Added: 20546
2012-08-20 12:48 c_schmitz Status assigned => closed
2012-08-20 12:48 c_schmitz Resolution reopened => fixed
2012-08-20 12:49 c_schmitz Note Edited: 20546