The FileSize column of the Entries table and all the API to acces it stores the filesizes as signed 32bit integer. This causes the entries filesize to be stored and display incorrectly when handling files > 2GB.
Would it be possible to have the database and API modified for the next release to use 64bit integers instead?