Conversion from digikam3.db to digikam4.db

Hi

Is there any tool to convert digikam3.db to digikam4.db ?
When I launch digikam on my previous album, I get an error dialog box
suggesting me to erase my digikam3.db file. Not a very good idea as I am
quite reluctant to re-tag several thousands of images.

the exact message  is :

The schema updating process from version 4 to 5 failed, caused by an
internal error. Please delete the database files ("digikam3.db" and
"digikam4.db" in "/home/photo_video/frederic/photos") if you want to try
to run digiKam with an empty database - it might work then.

Any clue ?

Regards

Frederic



_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Frederic Gedin a écrit :

Hi

Is there any tool to convert digikam3.db to digikam4.db ?
When I launch digikam on my previous album, I get an error dialog box 
suggesting me to erase my digikam3.db file. Not a very good idea as I am 
quite reluctant to re-tag several thousands of images.

the exact message  is :

The schema updating process from version 4 to 5 failed, caused by an 
internal error. Please delete the database files ("digikam3.db" and 
"digikam4.db" in "/home/photo_video/frederic/photos") if you want to try 
to run digiKam with an empty database - it might work then.
  

Hello,
 i recently installed mandriva 2009 which comes with kde4 and digikam 10.xx beta.
Before running this beta version i had made a backup of digikam3.db and the first time i ran version 10 it creates a digikam4.db file:

-rw-r--r--  1 michel michel  3107840 2008-10-14 09:57 digikam3.db.apresInstall2009
-rw-r--r--  1 michel michel 12561408 2008-10-15 13:48 digikam4.db

As digikam 10 is not an operational version i decided to install version 0.9.5: This version has read the initial digikam3db without problem (this means that this database file had not been corrupted by digikam 10). So I think that the correct tools to convert from digikam3.db to digikam4.db (or to create a digikam4.db) is digikam 10.0. Do you have a backup of 3.db to retry the conversion with digikam 10.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Marcel Wiesweg]

> Hi
>
> Is there any tool to convert digikam3.db to digikam4.db ?
> When I launch digikam on my previous album, I get an error dialog box
> suggesting me to erase my digikam3.db file. Not a very good idea as I am
> quite reluctant to re-tag several thousands of images.
>
> the exact message  is :
>
> The schema updating process from version 4 to 5 failed, caused by an
> internal error. Please delete the database files ("digikam3.db" and
> "digikam4.db" in "/home/photo_video/frederic/photos") if you want to try
> to run digiKam with an empty database - it might work then.
>
> Any clue ?
>
> Regards
>
> Frederic

Ok I agree that speaking of an "internal error" is the wrong way to present an
error message to a user (at least I did not print out an error code or
hexadecimal stack traces) ;-)

Please give the messages that are printed on the console when you try to
update the database file, those starting with "updateV4toV5"
(if  the file exists delete digikam4.db, never delete digikam3.db without a
backup of course)

Marcel
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Frederic Gedin a écrit :

> Hi
>
> Is there any tool to convert digikam3.db to digikam4.db ?
> When I launch digikam on my previous album, I get an error dialog box
> suggesting me to erase my digikam3.db file. Not a very good idea as I
> am quite reluctant to re-tag several thousands of images.
>
> the exact message  is :
>
> The schema updating process from version 4 to 5 failed, caused by an
> internal error. Please delete the database files ("digikam3.db" and
> "digikam4.db" in "/home/photo_video/frederic/photos") if you want to
> try to run digiKam with an empty database - it might work then.
>
> Any clue ?
>
> Regards
>
> Frederic
>
>

Here is the log of digikam when it fails :

digikam(2867): Root Album Path:  "/home/photo_video/frederic/photos"
digikam(2867): Database Path:  "/home/frederic/Pictures"
digikam(2867): SchemaUpdater update
digikam(2867): No database file available
digikam(2867): makeUpdates  4  to  5
digikam(2867): updateV4toV5
digikam(2867): Moved tables
digikam(2867): Dropped triggers
digikam(2867): addLocation  KUrl("file:///home/photo_video/frederic/photos")
digikam(2867): listFromType
digikam(2867): got listFromType
digikam(2867): Failed to detect a storage volume for path  
"/home/photo_video/frederic/photos"  with Solid

digikam(2867): Unable to identify a path with Solid. Adding the location
with path only.

digikam(2867): listFromType
digikam(2867): got listFromType
digikam(2867): Creating new Location  "/"  uuid  
"volumeid:?path=%2Fhome%2Fphoto_video%2Ffrederic%2Fphotos"
digikam(2867): location for  "/home/photo_video/frederic/photos/"  is
available true
digikam(2867): Testing location  1 "/home/photo_video/frederic/photos"
"/home/photo_video/frederic/photos/"
digikam(2867): Failure to create a collection location. Aborting update.

QSqlDatabasePrivate::removeDatabase: connection
'digikamDatabase-19021440' is still in use, all queries will cease to work.


Regards

Frederic


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Marcel Wiesweg]

> Here is the log of digikam when it fails :
>
> digikam(2867): Root Album Path:  "/home/photo_video/frederic/photos"
> digikam(2867): Database Path:  "/home/frederic/Pictures"
> digikam(2867): SchemaUpdater update
> digikam(2867): No database file available
> digikam(2867): makeUpdates  4  to  5
> digikam(2867): updateV4toV5
> digikam(2867): Moved tables
> digikam(2867): Dropped triggers
> digikam(2867): addLocation
> KUrl("file:///home/photo_video/frederic/photos") digikam(2867):
> listFromType
> digikam(2867): got listFromType
> digikam(2867): Failed to detect a storage volume for path
> "/home/photo_video/frederic/photos"  with Solid

Please check your installation, particularly that HAL is running.

>
> digikam(2867): Unable to identify a path with Solid. Adding the location
> with path only.
>
> digikam(2867): listFromType
> digikam(2867): got listFromType
> digikam(2867): Creating new Location  "/"  uuid
> "volumeid:?path=%2Fhome%2Fphoto_video%2Ffrederic%2Fphotos"
> digikam(2867): location for  "/home/photo_video/frederic/photos/"  is
> available true
> digikam(2867): Testing location  1 "/home/photo_video/frederic/photos"
> "/home/photo_video/frederic/photos/"
> digikam(2867): Failure to create a collection location. Aborting update.

This was probably due to a bug that is now fixed in SVN.
With current SVN, the behavior should be:
- if Solid is not returning any storage volumes (i.e. it's broken), fail early
- if Solid is returning volumes but for some case cannot identify on which one
your path is located, it will fall back as it did here, and that will now
probably work, which it did not for you.
- the generic error message for unexpected errors does not speak of "internal
errors" and does not suggest to delete your database file ;-)

Marcel
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Johannes]

Hello,

As I re-posted this issue without properly  checking the archives, I apologize. Reading them now, I made sure that hal and dbus are both running on my Debian unstable box running
> /usr/bin/digikam --version
> Qt: 4.4.3
> KDE: 4.1.3 (KDE 4.1.3)
> digiKam: 0.10.0-beta2

however, I still run into the same issue (see below).

Can anyone point me into where to look next? Is there a beta5 *.deb around somewhere?

Thanks for any hints!

Joh

In the shell:
        digikam(6416): makeUpdates  4  to  5
        digikam(6416): updateV4toV5
        digikam(6416): Moved tables
        digikam(6416): Dropped triggers
        digikam(6416): addLocation  KUrl("file:///home/family/Bilder/Archiv/jpg")
        digikam(6416): listFromType
        digikam(6416): got listFromType
        digikam(6416): Failed to detect a storage volume for path  
                "/home/family/Bilder/Archiv/jpg"  with Solid

        digikam(6416): Unable to identify a path with Solid. Adding the location
                with path only.

        digikam(6416): listFromType
        digikam(6416): got listFromType
        digikam(6416): Creating new Location  "/"  uuid  
                "volumeid:?path=%2Fhome%2Ffamily%2FBilder%2FArchiv%2Fjpg"
        digikam(6416): location for  "/home/family/Bilder/Archiv/jpg/"  is
                available  true
        digikam(6416): Testing location  1 "/home/family/Bilder/Archiv/jpg"
                "/home/family/Bilder/Archiv/jpg/"
        digikam(6416): Failure to create a collection location. Aborting update.
Gui error:
        The schema updating process from version 4 to 5 failed, caused by an
        internal error. Please delete the database files ("digikam3.db" and
        "digikam4.db" in "/home/family/Bilder/Archiv/jpg") if you want to try to
        run digiKam with an empty database - it might work then.
Process dialog:
        Opened new database file
        Prepared table creation
        Created tables
        Error


Marcel Wiesweg wrote:

>
>> Here is the log of digikam when it fails :
>>
>> digikam(2867): Root Album Path:  "/home/photo_video/frederic/photos"
>> digikam(2867): Database Path:  "/home/frederic/Pictures"
>> digikam(2867): SchemaUpdater update
>> digikam(2867): No database file available
>> digikam(2867): makeUpdates  4  to  5
>> digikam(2867): updateV4toV5
>> digikam(2867): Moved tables
>> digikam(2867): Dropped triggers
>> digikam(2867): addLocation
>> KUrl("file:///home/photo_video/frederic/photos") digikam(2867):
>> listFromType
>> digikam(2867): got listFromType
>> digikam(2867): Failed to detect a storage volume for path
>> "/home/photo_video/frederic/photos"  with Solid
>
> Please check your installation, particularly that HAL is running.
>
>>
>> digikam(2867): Unable to identify a path with Solid. Adding the location
>> with path only.
>>
>> digikam(2867): listFromType
>> digikam(2867): got listFromType
>> digikam(2867): Creating new Location  "/"  uuid
>> "volumeid:?path=%2Fhome%2Fphoto_video%2Ffrederic%2Fphotos"
>> digikam(2867): location for  "/home/photo_video/frederic/photos/"  is
>> available true
>> digikam(2867): Testing location  1 "/home/photo_video/frederic/photos"
>> "/home/photo_video/frederic/photos/"
>> digikam(2867): Failure to create a collection location. Aborting update.
>
> This was probably due to a bug that is now fixed in SVN.
> With current SVN, the behavior should be:
> - if Solid is not returning any storage volumes (i.e. it's broken), fail
> early - if Solid is returning volumes but for some case cannot identify on
> which one your path is located, it will fall back as it did here, and that
> will now probably work, which it did not for you.
> - the generic error message for unexpected errors does not speak of
> "internal errors" and does not suggest to delete your database file ;-)
>
> Marcel

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Johannes]

Temporarily remidied this by installing kde3.5 digikam in a chroot.

Joh

Johannes Graumann wrote:

> Hello,
>
> As I re-posted this issue without properly  checking the archives, I
> apologize. Reading them now, I made sure that hal and dbus are both
> running on my Debian unstable box running
>> /usr/bin/digikam --version
>> Qt: 4.4.3
>> KDE: 4.1.3 (KDE 4.1.3)
>> digiKam: 0.10.0-beta2
>
> however, I still run into the same issue (see below).
>
> Can anyone point me into where to look next? Is there a beta5 *.deb around
> somewhere?
>
> Thanks for any hints!
>
> Joh
>
> In the shell:
> digikam(6416): makeUpdates  4  to  5
> digikam(6416): updateV4toV5
> digikam(6416): Moved tables
> digikam(6416): Dropped triggers
> digikam(6416): addLocation  KUrl("file:///home/family/Bilder/Archiv/jpg")
> digikam(6416): listFromType
> digikam(6416): got listFromType
> digikam(6416): Failed to detect a storage volume for path
> "/home/family/Bilder/Archiv/jpg"  with Solid
>
> digikam(6416): Unable to identify a path with Solid. Adding the location
> with path only.
>
> digikam(6416): listFromType
> digikam(6416): got listFromType
> digikam(6416): Creating new Location  "/"  uuid
> "volumeid:?path=%2Fhome%2Ffamily%2FBilder%2FArchiv%2Fjpg"
> digikam(6416): location for  "/home/family/Bilder/Archiv/jpg/"  is
> available  true
> digikam(6416): Testing location  1 "/home/family/Bilder/Archiv/jpg"
> "/home/family/Bilder/Archiv/jpg/"
> digikam(6416): Failure to create a collection location. Aborting update.
> Gui error:
> The schema updating process from version 4 to 5 failed, caused by an
> internal error. Please delete the database files ("digikam3.db" and
> "digikam4.db" in "/home/family/Bilder/Archiv/jpg") if you want to try to
> run digiKam with an empty database - it might work then.
> Process dialog:
> Opened new database file
> Prepared table creation
> Created tables
> Error
>
>
> Marcel Wiesweg wrote:
>
>>
>>> Here is the log of digikam when it fails :
>>>
>>> digikam(2867): Root Album Path:  "/home/photo_video/frederic/photos"
>>> digikam(2867): Database Path:  "/home/frederic/Pictures"
>>> digikam(2867): SchemaUpdater update
>>> digikam(2867): No database file available
>>> digikam(2867): makeUpdates  4  to  5
>>> digikam(2867): updateV4toV5
>>> digikam(2867): Moved tables
>>> digikam(2867): Dropped triggers
>>> digikam(2867): addLocation
>>> KUrl("file:///home/photo_video/frederic/photos") digikam(2867):
>>> listFromType
>>> digikam(2867): got listFromType
>>> digikam(2867): Failed to detect a storage volume for path
>>> "/home/photo_video/frederic/photos"  with Solid
>>
>> Please check your installation, particularly that HAL is running.
>>
>>>
>>> digikam(2867): Unable to identify a path with Solid. Adding the location
>>> with path only.
>>>
>>> digikam(2867): listFromType
>>> digikam(2867): got listFromType
>>> digikam(2867): Creating new Location  "/"  uuid
>>> "volumeid:?path=%2Fhome%2Fphoto_video%2Ffrederic%2Fphotos"
>>> digikam(2867): location for  "/home/photo_video/frederic/photos/"  is
>>> available true
>>> digikam(2867): Testing location  1 "/home/photo_video/frederic/photos"
>>> "/home/photo_video/frederic/photos/"
>>> digikam(2867): Failure to create a collection location. Aborting update.
>>
>> This was probably due to a bug that is now fixed in SVN.
>> With current SVN, the behavior should be:
>> - if Solid is not returning any storage volumes (i.e. it's broken), fail
>> early - if Solid is returning volumes but for some case cannot identify
>> on which one your path is located, it will fall back as it did here, and
>> that will now probably work, which it did not for you.
>> - the generic error message for unexpected errors does not speak of
>> "internal errors" and does not suggest to delete your database file ;-)
>>
>> Marcel

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users