dK 5.7.0 Error converting database (haar matrix)

[Richard Mortimer]

Hi,

I haven't had chance to check yet but suspect a number of the original
failure scenarios that we had with MySQL to MySQL migration have been
broken by the recent changes.

It now seems to be only checking for the presence of associated images
in the old database. We have see issues involving images that no longer
had an associated Album or even images in Albums where the Album Root
had been deleted. The query logic that protected against that should
have been directly transferable to SQLite (indeed I was planning on
testing that when my laptop died a few months back). I got my laptop
mended a short while ago and will try to see how the latest changes cope
with my old digikam 4 databases.

Regards

Richard

On 04/12/2017 14:19, Gilles Caulier wrote:
> Hi,
> 
> A lots of work have be done to next 5.8.0 about Mysql support and
> migration tool. The current pre-release AppImage bundle can be tested here :
> 
> https://files.kde.org/digikam/
> 
> Gilles Caulier
> 
> 2017-12-04 14:33 GMT+01:00 J Albrecht <heviiguy at gmail.com
> <mailto:heviiguy at gmail.com>>:
> 
>     I’ve tried to convert my database from SQLite to MySQL twice. Both
>     attempts appeared to be going well until approximately 75% into the
>     process. At those times, they failed with the following dialogue:
> 
>     Error while converting the database. Details: Cannot add or update a
>     child row: a foreign key constraint fails
>     (`digikam`.`ImageHaarMatrix`, CONSTRAINT `ImageHaarMatrix_Images`
>     FOREIGN KEY (`imageid`) REFERENCES `Images` (`id`) ON DELETE CASCADE
>     ON UPDATE CASCADE)
> 
>     Any idea how I might be able to overcome this critical issue?
> 
>