[Digikam-devel] [Bug 276171] New: Cannot migrate from mysql to mysql

Frederic Grelot fredericg_99 at yahoo.fr
Tue Jun 21 07:46:37 BST 2011


https://bugs.kde.org/show_bug.cgi?id=276171

           Summary: Cannot migrate from mysql to mysql
           Product: digikam
           Version: 2.0.0
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Database
        AssignedTo: digikam-devel at kde.org
        ReportedBy: fredericg_99 at yahoo.fr


Version:           2.0.0 (using KDE 4.6.4) 
OS:                Linux

This is created from bug #276052 (which describes actually 2 bugs).
When migrating from mysql to mysql (using different table names), the upgrade
fails at "Create Schema".
This is due to the fact that SchemeUpdater tries to read the version number
from the Settings table of the "toBackend", and uses this value in
"SchemaUpdater::setVersionSettings()"

The following queries show the SchemeUpdater trying to read the version number,
and come from the mysql log (digikam is the source database, while digikam2 is
the target database) :
           92 Init DB    digikam
           92 Query    SET NAMES utf8
           93 Connect    digikam at laptop on digikam2
           93 Init DB    digikam2
           93 Query    SET NAMES utf8
           93 Query    DROP TABLE IF EXISTS AlbumRoots, Albums,
DownloadHistory, FilePaths, ImageComments, ImageCopyright, ImageHaarMatrix,
ImageInformation, ImageMetadata, ImagePositions, ImageProperties, ImageTags,
Images, Searches, Settings, Tags, TagsTree, Thumbnails, UniqueHashes
           94 Connect    digikam at laptop on digikam2
           94 Init DB    digikam2
           94 Query    SET NAMES utf8
           94 Query    CREATE TABLE IF NOT EXISTS PrivCheck
                (
                    id   INT,
                   name VARCHAR(35)
                )
           94 Query    ALTER TABLE PrivCheck DROP COLUMN name
110619 15:37:02       94 Query    CREATE TRIGGER privcheck_trigger AFTER DELETE
ON PrivCheck
                  FOR EACH ROW BEGIN
                  END
           94 Query    DROP TRIGGER privcheck_trigger
           94 Query    DROP TABLE PrivCheck
           94 Query    DROP TABLE IF EXISTS PrivCheck
           94 Quit    
           93 Query    select table_name from information_schema.tables where
table_type = 'BASE TABLE'
           93 Query    SELECT value FROM Settings WHERE keyword='DBVersion'
           93 Query    SELECT value FROM Settings WHERE
keyword='DBVersionRequired'
           92 Quit    
           93 Quit   

Reproducible: Didn't try

Steps to Reproduce:
-Have a mysql database (from version 1.9)
-migrate it with digikam 2.0.0b6 to another mysql DB

Actual Results:  
No migration : error while creating schema

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Digikam-devel mailing list