[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 295103] New: SQL backend conversion fails on some databases
From:       Johannes Zarl <isilmendil () gmx ! net>
Date:       2012-02-29 22:42:39
Message-ID: bug-295103-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

           Summary: SQL backend conversion fails on some databases
           Product: kphotoalbum
           Version: GIT master
          Platform: Unlisted Binaries
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: SQL backend
        AssignedTo: kpabugs@willden.org
        ReportedBy: isilmendil@gmx.net


Created an attachment (id=69195)
 --> (http://bugs.kde.org/attachment.cgi?id=69195)
A minimal xml database showing the problem

Version:           GIT master
OS:                Linux

Backend conversion fails with my XML database, and reports the following
message:

> Database conversion failed, because following error occurred:
> QtSQLError: Error while excuting an insert statement. The query was "INSERT
> INTO tag(category_id, name) VALUES (?, ?)". Bindinds are (1,). The text of 
> QSqlError is "tag.name may not be NULL Unable to fetch row"

Reproducible: Always

Steps to Reproduce:
Use attached minimal index.xml, and select "Convert backend" from the
maintenance menu. If neccessary, select a file for the SQLite database.

Actual Results:  
Conversion fails with the above error message. Additionally, the following
console output is written:

> Inserting info of file /home/zing/Bilder/storage/2004/Suomi/01-Ankunft/01-Flugzeug.jpg

Expected Results:  
A succesful import.

The convertBackend method seems to choke on the 'Token="0"' entry. Removing
those entries manually from my real index.xml allows kphotoalbum to convert the
database without errors.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]