Opened 13 years ago

Closed 13 years ago

#3419 closed defect (fixed)

MythArchive archiveitem database scheme truncates file sizes at 4GB

Reported by: anonymous Owned by: paulh
Priority: minor Milestone: unknown
Component: mytharchive Version: head
Severity: low Keywords:
Cc: Ticket locked: no

Description

MythArchive? can generally handle files over 4GB in size, however the size column of the archiveitems is only an unsigned int and thus has a maximum value of 4GB. MySql? will truncate larger values when they are inserted.

Attached is a simple patch to fix the problem.

Attachments (1)

mytharchive_filesize_patch.diff (1.3 KB) - added by rd.mora@… 13 years ago.
Patch to increase the capacity of the size field in the archiveitems table.

Download all attachments as: .zip

Change History (3)

Changed 13 years ago by rd.mora@…

Patch to increase the capacity of the size field in the archiveitems table.

comment:1 Changed 13 years ago by paulh

This patch isn't quite right. It works but more by luck than judgment I think. It will remove the existing table completely and replace it with the new one deleting any records in the table in the process. The proper way to do it is to just alter the column type which will leave the records if any exist intact.

comment:2 Changed 13 years ago by paulh

Resolution: fixed
Status: newclosed

(In [13428]) Increase the size column in the archiveitems table from INT to BIGINT. Allows MythArchive? to work with files larger than 4Gb.

Closes #3419.

Note: See TracTickets for help on using tickets.