Hi Sylvain I think the migration from integer to bigint in the file_size could be a futture mod. In the new environments the systems demands more and more biggest files and could be interesting to have implemented this on FF. The example of the virtual machines uploaded for deploy a source project it's clearly.
What is the manner of work with the use_manual_uploads? I don't have worked with it... On which directory goes the bigfile? /var/fusionforge/download/GROUP?? Must we have to introduce the filesize on this manner or evade to check this point? Do we need to register manually this kind of file? Thanks a lot!! Enviado con MailTrack <https://mailtrack.io/install?source=signature&lang=es&referral=joseangel.d...@cenatic.es&idSignature=23> 2014-06-02 11:19 GMT+02:00 Sylvain Beucler - Inria <sylvain.beuc...@inria.fr >: > Hi, > > In your situation I'd recommend to upload using the group's "incoming" > directory (use_manual_uploads = yes). > > Aside from that, if you want to support 64-bit file size, the limitation > may come from a lot of different places. > I believe FusionForge itself will work with your DB change, but you need > to test :) > > - Sylvain > > Le 02/06/2014 11:04, Jose Angel Diaz a écrit : > > Hi Sylvain > > We have a 5.2 Forge. > > For this kind of special 'large' files we have a handwork to do in > manual mode. > > We upload a dummy file with 0 kb to make the database changes > > We upload the new file to > the :/var/lib/fusionforge/download/Project/doc/version > > Then we make the postgresql in manual manner: > > UPDATE frs_file set file_size=790973396 WHERE file_id=xyz > > On this way the fusionforge don't make any truncate file, in the apache > side the download size it's increased. > > The big problem today its the file_size, in a new environment with > virtualmachines for testing the file_size on this column is obsolete > > I've been watching the table and the view and initially i'm going to > make this changes: > > Create a copy of the view frs_file_vw > Drop the view frs_file_vw > Alter column frs_file:file_size > Create a new view with frs_file_vw attributtes > > My big question is the internal fusionforge management of this view, > apparently this change doesn't affect the content, but i don't know about > the frs management. > > Regards!! > > > 2014-06-02 10:32 GMT+02:00 Sylvain Beucler - Inria < > sylvain.beuc...@inria.fr>: > >> Hi, >> >> Le 30/05/2014 14:13, Jose Angel Diaz a écrit : >> >> Hi!! >>> >>> We have a production forge where the communities are uploading big >>> binaries files to File Section in fusionforge. >>> >>> The Problem we have find is that the frs_size in frs_file is integer >>> but the images are bigger than the postgres integer limits: -2147483648 to >>> +2147483647 >>> Could be possible to alter the frs_file table and the frs_size to bigint >>> (-9223372036854775808 to 9223372036854775807) whithout make a crash on the >>> platform fusionforge? >>> >> >> It seems like a good idea. >> I'd like to understand better the problem though: >> - What is your FusionForge version? >> - Where do you get a problem: can you upload a large file? If yes, can >> you download that large file, or is it truncated? >> >> >> >> Could it affects to the fusionforge performance? >>> >> >> The files are stored on disk, so I think not :) >> > -- --------------------------------------------------------------------------------------------------------- Correo Corporativo Fundación Cenatic Este email ha sido enviado desde una plataforma perteneciente a la Fundación Cenatic Cualquier duda o modificacion contactar con Fundación Cenatic +34 924 67 73 16 i...@cenatic.es
_______________________________________________ Fusionforge-general mailing list Fusionforge-general@lists.fusionforge.org http://lists.fusionforge.org/cgi-bin/mailman/listinfo/fusionforge-general
