[digikam] [Bug 323062] New: digikam (core): Schema update to V 7 failed!

classic Classic list List threaded Threaded
26 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 323062] digikam (core): Schema update to V 7 failed!

Marcel Wiesweg
https://bugs.kde.org/show_bug.cgi?id=323062

--- Comment #18 from Marcel Wiesweg <[hidden email]> ---
I agree. upgradeV4toV6 is essentially like creating a fresh database and doing
some importing into the empty tables, so it ends up at the latest version. I
would not like to have another large a historic createTablesV6 for this, as far
as I see it's easily fixed by recognizing the updateV4toV6 is properly named
updateV4toV7

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 323062] digikam (core): Schema update to V 7 failed!

Marcel Wiesweg
In reply to this post by Rainer Dorsch-2
https://bugs.kde.org/show_bug.cgi?id=323062

Marcel Wiesweg <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED
      Latest Commit|                            |http://commits.kde.org/digi
                   |                            |kam/b4f815763e7233ee84aac95
                   |                            |32fd903a4e10427a5

--- Comment #19 from Marcel Wiesweg <[hidden email]> ---
Git commit b4f815763e7233ee84aac9532fd903a4e10427a5 by Marcel Wiesweg.
Committed on 25/08/2013 at 12:31.
Pushed by mwiesweg into branch 'master'.

Fix schema updates from old versions: updatev4tov6 is updatev4tov7

M  +6    -4    libs/database/schemaupdater.cpp
M  +1    -1    libs/database/schemaupdater.h

http://commits.kde.org/digikam/b4f815763e7233ee84aac9532fd903a4e10427a5

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
TSa
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 323062] digikam (core): Schema update to V 7 failed!

TSa
In reply to this post by Rainer Dorsch-2
https://bugs.kde.org/show_bug.cgi?id=323062

--- Comment #20 from TSa <[hidden email]> ---
HaloO Marcel,

great to hear that the bug is fixed! And I hope you keep an eye on it for
future schema updates. Because then you might need to rename the function
to updateV4toV8 if that still fits the bill or do something more sophisticated
depending on the changes in the schema.

I can live with my patched 3.2 on kubuntu 13.04 for now and I think at the time
of an update to 13.10 which currently has digikam 3.3 my schema will be already
on V7. So the bug will be irrelevant to me.

Should I keep my old digikam file for regression testing or do you have an
environment
where you can check the version transitions? BTW, is it sufficient to keep the
digikam3.db
file or do I need all the photos in the right place?

Regards TSa.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 323062] digikam (core): Schema update to V 7 failed!

Marcel Wiesweg
In reply to this post by Rainer Dorsch-2
https://bugs.kde.org/show_bug.cgi?id=323062

--- Comment #21 from Marcel Wiesweg <[hidden email]> ---
 As you see with this bug, I did not do regression test with combinations of
old versions. And I have no special environment set up.
I would think it better to have the photos in the old place, did not try what
happens if not.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 323062] digikam (core): Schema update to V 7 failed!

Marcel Wiesweg
In reply to this post by Rainer Dorsch-2
https://bugs.kde.org/show_bug.cgi?id=323062

--- Comment #22 from Marcel Wiesweg <[hidden email]> ---
Short guidance for anyone wishing to repair his database:

Open the digikam4.db file with the sqlite3 command line tool:
sqlite3 <path>/digikam4.db

Make sure this bug is for you:
SELECT * FROM Settings WHERE keyword='DBVersion';
DBVersion|6
SELECT COUNT(*) FROM VideoMetadata;
0

The latter statement should give any number, and not the error "no such table:
VideoMetadata"

If that applies, fix your DBVersion:

REPLACE INTO Settings (keyword, value) VALUES ('DBVersion', 7);
.exit

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 323062] digikam (core): Schema update to V 7 failed!

bugzilla_noreply
In reply to this post by Rainer Dorsch-2
https://bugs.kde.org/show_bug.cgi?id=323062

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Database                    |Database-Schema

--
You are receiving this mail because:
You are the assignee for the bug.
12