Bug 402380 - Database schema upgrade to V10 is incomplete
Summary: Database schema upgrade to V10 is incomplete
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Database-Mysql (show other bugs)
Version: 6.0.0
Platform: Appimage Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-20 13:27 UTC by meku
Modified: 2018-12-20 19:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 6.0.0
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description meku 2018-12-20 13:27:06 UTC 
SUMMARY

Beginning with a DK5.9 database and then running the latest DK6.0b3 (20181215) the database schema is upgraded to v10 but there are many fields that are not updated to the same level as a clean install of DK6.0 

For example in v10 many of the INT fields have been changed to BIGINT and DATETIME has been changed to DATETIME(3).

STEPS TO REPRODUCE
1. Install DK5.9 with MySQL database
2. Run DK6.0

OBSERVED RESULT
Database version is upgraded to v10 but the above fields are not updated.

EXPECTED RESULT
Database is upgraded to identical structure as a fresh install of DK6.0

ADDITIONAL INFORMATION
Having INT instead of BIGINT does not appear to be causing any further issues at this time, however the omission of DATETIME(3) appears to be partly responsible for Bug #402379
Comment 1 Maik Qualmann 2018-12-20 14:05:53 UTC 
The changes INT to BIGINT and DATETIME(3) are an investment in the future and have no influence on the function of digiKam. It is definitely not intended to apply this to existing databases. DATETIME(3) is supported only with newer versions of MySQL.

Maik