Digikam-users Digest, Vol 138, Issue 33

[Gilles Caulier]

Ok perfect analyze.

Please create a new report in KDE bugzilla with these information (section
digiKam/database). We will process it in release workflow. Thanks in advance

Gilles Caulier

2016-11-15 23:40 GMT+01:00 Brian J Hoskins <brian at hoskins.eu>:

> Dear Gilles,
>
> In the "Images" table there is a field called "fileSize".  When the
> database is created, this is of type int.  Since type int is 32-bit, I
> wondered if this would impose a 4GB (2^32) limit on the fileSize
> record.  So I changed it to bigint (64-bit) and this indeed allowed
> digikam to add the file.
> I had to change the field type "on the fly", while the database
> migration was running (but after the schema is created), because digikam
> resets it to int each time the migration is started.  I was able to make
> the change before digikam encountered the large file and this worked.
>
> Since the error dialogue does not tell me which file it was complaining
> about, I can't say exactly what file triggered the error.
> But to test my thinking further, I created a fresh SQLite database with
> only one file in it; a 5.2GB mp4 file.  I then tried to migrate that
> database and I encountered the same error.  So I think I was right about
> the 4GB limit.
>
>
> Best Regards,
>
>
> Brian.
>
>
> On 15/11/16 12:00, digikam-users-request at kde.org wrote:
> > What do you change exactly in table ? Which video file size do you have
> to
> > have this kind of overrun ?
> >
> > Gilles caulier
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20161116/55671649/attachment.html>