Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: storage_service locations_package.size is not big enough, should be BigIntegerField #120

Closed
vdecorges opened this issue Aug 28, 2018 · 1 comment

Comments

@vdecorges
Copy link

Expected behaviour
When storing file larger than 2^31-1 into the Storage_Service the acutal ize of the AIP or DIP should be stored.

Current behaviour
Currently when an AIP or DIP is stored that is larger than 2^31-1 the size is 2^31-1 and not the real size of the file.

Steps to reproduce
Store into the Storage_Service a file larger than 2^31-1 bytes. Note that the problem occurs only with MySQL as DB for the Storage_Service.

The correction is to change that datatype of locations_package.size to django.db.models.fields.BigIntegerField

Your environment (version of Archivematica, OS version, etc)
Archivematica v 1.7, Storage Service v 0.11 and MySQL for the Storage Service

@vdecorges vdecorges changed the title Storage_service: locations_package.size is not big enough, should be BigIntegerField Problem: storage_service locations_package.size is not big enough, should be BigIntegerField Aug 29, 2018
@eviau-artefactual
Copy link

Hello @vdecorges - thank you for your patience.

We realized this should be fixed by commit artefactual/archivematica-storage-service@d54716c from the Issue #981

We will close this issue for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants