Digikam 5.3.0-01 database migration: Out of Range value for column 'fileSize'

[Brian J Hoskins-2]

Hello digiKam users.

I am trying out version 5.3 of digiKam for the first time, using the
Application Bundle.  Previously I have used version 4.12 and I have an
existing SQLite database.

When trying to migrate the database I get to around 30% completion when
the following error is reported:

"Error while converting the database.
Details: Out of range value for column 'fileSize' at row 1"

I have quite a few video files in the database, and I wonder if one of
these is larger than the database was expecting.

Unfortunately the migration tool gives up at this point, so I am not
able to get more information about the problem or even skip and continue.

Does anyone have useful advice to offer here?

Many thanks,

Brian.

[Brian J Hoskins-2]

I solved the problem below by changing the variable type for 'fileSize' in the images table to BigInt.  But then it got to 99% and complained about a file name of some description.  It would be useful if the migration tool offered the name of the offending file in the error dialogue.

On 14/11/16 20:37, Brian J Hoskins wrote:

Hello digiKam users.

I am trying out version 5.3 of digiKam for the first time, using the
Application Bundle.  Previously I have used version 4.12 and I have an
existing SQLite database.

When trying to migrate the database I get to around 30% completion when
the following error is reported:

"Error while converting the database.
Details: Out of range value for column 'fileSize' at row 1"

I have quite a few video files in the database, and I wonder if one of
these is larger than the database was expecting.

Unfortunately the migration tool gives up at this point, so I am not
able to get more information about the problem or even skip and continue.

Does anyone have useful advice to offer here?

Many thanks,

Brian.

[Gilles Caulier-4]

What do you change exactly in table ? Which video file size do you have to have this kind of overrun ?

Gilles caulier

Le lun. 14 nov. 2016 à 22:23, Brian J Hoskins <[hidden email]> a écrit :

I solved the problem below by changing the variable type for 'fileSize' in the images table to BigInt.  But then it got to 99% and complained about a file name of some description.  It would be useful if the migration tool offered the name of the offending file in the error dialogue.

On 14/11/16 20:37, Brian J Hoskins wrote:

Hello digiKam users.

I am trying out version 5.3 of digiKam for the first time, using the
Application Bundle.  Previously I have used version 4.12 and I have an
existing SQLite database.

When trying to migrate the database I get to around 30% completion when
the following error is reported:

"Error while converting the database.
Details: Out of range value for column 'fileSize' at row 1"

I have quite a few video files in the database, and I wonder if one of
these is larger than the database was expecting.

Unfortunately the migration tool gives up at this point, so I am not
able to get more information about the problem or even skip and continue.

Does anyone have useful advice to offer here?

Many thanks,

Brian.

--

[Brian J Hoskins-2]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear Gilles,

I have submitted the bug at:
https://bugs.kde.org/buglist.cgi?component=Database&product=digikam&reso
lution=---

I have not submitted a bug report before, so I hope this is what you
meant by "bugzilla".  If not please can you point me in the right
direction?

Also I welcome constructive criticism about the bug report (and about
anything else, in fact).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJYLvT8AAoJEM0GjsMCIKklWKAH/3S25tstMmX5uMiDt3Z/iCgv
NsZhk7eeOb9o4aQGuJRqWTy/VcOEENvutAcB25Jhi7lEwFxZ9BwXHbJj5ZDgUcXE
Ztr5xohSzRZ8mkP4VSWa98QWo2CRx97DB/nDu8qP+CJThOHETTAcKwJzijfeMJz9
S5FG7F6avZK/Zi20bTfM6VPLTW2WmX8Mc6DLY2tnGQJbZN5ms1OHqd+5ExUhEWYi
NqjZo7I02oAEUoRMhnJZosHvguHG4MIrLXkv6VruMYYEbRuw3ZqhbIotr2S8CW9F
+4wJ2HlMid2op55t0kIn5THMs4ZuhAc7C8DjhIA6hnXE00R7OPB0coWW0YmbQ1o=
=1g6u
-----END PGP SIGNATURE-----

[Gilles Caulier-4]

yes it fine. I see the entry in bugzilla.

Gilles Caulier

2016-11-18 13:33 GMT+01:00 Brian J Hoskins <[hidden email]>:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear Gilles,

I have submitted the bug at:
https://bugs.kde.org/buglist.cgi?component=Database&product=digikam&reso
lution=---

I have not submitted a bug report before, so I hope this is what you
meant by "bugzilla".  If not please can you point me in the right
direction?

Also I welcome constructive criticism about the bug report (and about
anything else, in fact).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJYLvT8AAoJEM0GjsMCIKklWKAH/3S25tstMmX5uMiDt3Z/iCgv
NsZhk7eeOb9o4aQGuJRqWTy/VcOEENvutAcB25Jhi7lEwFxZ9BwXHbJj5ZDgUcXE
Ztr5xohSzRZ8mkP4VSWa98QWo2CRx97DB/nDu8qP+CJThOHETTAcKwJzijfeMJz9
S5FG7F6avZK/Zi20bTfM6VPLTW2WmX8Mc6DLY2tnGQJbZN5ms1OHqd+5ExUhEWYi
NqjZo7I02oAEUoRMhnJZosHvguHG4MIrLXkv6VruMYYEbRuw3ZqhbIotr2S8CW9F
+4wJ2HlMid2op55t0kIn5THMs4ZuhAc7C8DjhIA6hnXE00R7OPB0coWW0YmbQ1o=
=1g6u
-----END PGP SIGNATURE-----